Location of a mobile device with wireless access using a user plane location solution

ABSTRACT

Techniques are discussed herein for supporting location of a user equipment (UE) with wireless access using a user plane (UP) location solution like SUPL. To locate the UE, an initial UP location session is established between the UE and a location server (LS) during which the LS requests location measurements from the UE. The UE obtains the location measurements by ending the location session and entering an idle state, after indicating this intent to the LS. The UE sends the location measurements to the LS by reentering a connected state and starting a new UP location session with the LS, which may be associated with the initial location session using common identification information. The techniques may be used for a UE with only a single RF chain (e.g. a UE that supports NB-IoT or other narrowband wireless access).

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.62/672,568, entitled “SYSTEMS AND METHODS FOR SUPPORT OF LOCATION FORNB-IOT UEs USING SUPL,” filed May 16, 2018, which is assigned to theassignee hereof and which is expressly incorporated herein by referencein its entirety.

BACKGROUND Field

Subject matter disclosed herein relates to estimation of a location of amobile device and more particularly to location of a mobile device thatconnects to a wireless network with user plane location services.

Information

The location of a mobile device, such as a cellular telephone, may beuseful or essential to a number of applications including emergencycalls, navigation, direction finding, asset tracking and Internetservice. The location of a mobile device may be estimated based oninformation gathered from various systems and using different locationsolutions. One location solution, which has been defined by the OpenMobile Alliance (OMA), is known as Secure User Plane Location (SUPL) andemploys signaling, conveyed at a user plane level, between a mobiledevice and a location server to coordinate the location of the mobiledevice. For a mobile device supporting Narrow Band Internet of Things(NB-IoT) wireless access, the mobile device may have only one radioreceiver (RF chain) to reduce cost and power (e.g., battery) usage. Thismay prevent the mobile device from obtaining certain locationmeasurements (e.g. GNSS or WLAN location measurements) while interactingwith a SUPL location server, since the single RF chain may need to bededicated to either signaling or location measurements but not to bothat the same time. This conflict could interfere with mobile devicelocation using SUPL and potentially could prevent location of the mobiledevice. It may thus be an advantage to develop techniques capable ofbetter supporting location of a mobile device with NB-IoT access usingSUPL.

SUMMARY

In one aspect, a method for supporting location services for a userequipment (UE) performed by the UE, includes beginning a first userplane location session with a location server; receiving a request forlocation measurements from the location server; sending an indication tothe location server that the UE will enter an idle state in which the UEwill not be connected with a wireless network; ending the first userplane location session with the location server; entering the idlestate; obtaining the location measurements while in the idle state;re-entering a connected state with the wireless network; beginning asecond user plane location session with the location server; and sendingthe location measurements to the location server using the second userplane location session.

In one aspect, a user equipment (UE) capable of supporting locationservices, includes at least one wireless transceiver configured towirelessly communicate with a wireless network; and at least oneprocessor coupled to the at least one wireless transceiver andconfigured to begin via the at least one wireless transceiver a firstuser plane location session with a location server; receive via the atleast one wireless transceiver a request for location measurements fromthe location server, send via the at least one wireless transceiver anindication to the location server that the UE will enter an idle statein which the UE will not be connected with the wireless network, end viathe at least one wireless transceiver the first user plane locationsession with the location server, enter the idle state, obtain via theat least one wireless transceiver the location measurements while in theidle state, re-enter a connected state with the wireless network, beginvia the at least one wireless transceiver a second user plane locationsession with the location server, and send via the at least one wirelesstransceiver the location measurements to the location server using thesecond user plane location session.

In one aspect, a user equipment (UE) capable of supporting locationservices, includes means for beginning a first user plane locationsession with a location server; means for receiving a request forlocation measurements from the location server; means for sending anindication to the location server that the UE will enter an idle statein which the UE will not be connected with a wireless network; means forending the first user plane location session with the location server;means for entering the idle state; means for obtaining the locationmeasurements while in the idle state; means for re-entering a connectedstate with the wireless network; means for beginning a second user planelocation session with the location server; and means for sending thelocation measurements to the location server using the second user planelocation session.

In one aspect, a non-transitory storage medium including program codestored thereon, the program code is operable to cause at least oneprocessor in a user equipment (UE) capable of supporting locationservices to: begin a first user plane location session with a locationserver; receive a request for location measurements from the locationserver; send an indication to the location server that the UE will enteran idle state in which the UE will not be connected with a wirelessnetwork; end the first user plane location session with the locationserver; enter the idle state; obtain the location measurements while inthe idle state; re-enter a connected state with the wireless network;begin a second user plane location session with the location server; andsend the location measurements to the location server using the seconduser plane location session.

BRIEF DESCRIPTION OF THE FIGURES

Claimed subject matter is particularly pointed out and distinctlyclaimed in the concluding portion of the specification. However, both asto organization and/or method of operation, together with featuresand/or advantages thereof, it may best be understood by reference to thefollowing detailed description if read with the accompanying drawings inwhich:

FIG. 1 is a system diagram illustrating certain features of a FourthGeneration (4G) communication system comprising a mobile device and acellular network, in accordance with an example implementation;

FIG. 2 is a system diagram illustrating certain features of a FifthGeneration (5G) communication system comprising a mobile device and acellular network, in accordance with an alternative exampleimplementation;

FIGS. 3 and 4 show a signaling flow illustrating a process ofdetermining a location for a user equipment (UE) with NB-IoT wirelessaccess for a Network Initiated SUPL session;

FIGS. 5 and 6 show a signaling flow illustrating a process ofdetermining a location for a UE with NB-IoT wireless access for a UEInitiated SUPL session;

FIG. 7 shows a process flow illustrating a method of supporting locationservices for a UE performed by the UE;

FIG. 8 shows a process flow 800 illustrating a method of supportinglocation services for a user equipment (UE) performed by a locationserver;

FIG. 9 is a diagram illustrating an example of a hardware implementationof UE configured for supporting location services as described herein;and

FIG. 10 is a diagram illustrating an example of a hardwareimplementation of a location server configured for supporting locationservices for a UE as described herein.

Reference is made in the following detailed description to the aboveaccompanying drawings, which form a part hereof, wherein like numericand alphanumeric labels may designate like parts throughout that areidentical, similar and/or analogous. In addition, multiple instances ofan element may be indicated by following a first number for the elementwith a hyphen and a second number. For example, multiple instances of anelement 210 may be indicated as 210-1, 210-2, 210-3 etc. When referringto such an element using only the first number, any instance of theelement is to be understood (e.g. element 210 in the previous examplewould refer any of the elements 210-1, 210-2 and 210-3).

It will be appreciated that the figures have not necessarily been drawnto scale, such as for simplicity and/or clarity of illustration. Forexample, dimensions of some aspects may be exaggerated relative toothers. Further, it is to be understood that other embodiments may beutilized. Furthermore, structural and/or other changes may be madewithout departing from claimed subject matter. References throughoutthis specification to “claimed subject matter” refer to subject matterintended to be covered by one or more claims, or any portion thereof,and are not necessarily intended to refer to a complete claim set, to aparticular combination of claim sets (e.g., method claims, apparatusclaims, etc.), or to a particular claim. It should also be noted thatdirections and/or references, for example, such as up, down, top,bottom, and so on, may be used to facilitate discussion of drawings andare not intended to restrict application of claimed subject matter.Therefore, the following detailed description is not to be taken tolimit claimed subject matter and/or equivalents.

DETAILED DESCRIPTION

References throughout this specification to one implementation, animplementation, one embodiment, an embodiment, and/or the like mean thata particular feature, structure, characteristic, and/or the likedescribed in relation to a particular implementation and/or embodimentis included in at least one implementation and/or embodiment of claimedsubject matter. Thus, appearances of such phrases, for example, invarious places throughout this specification are not necessarilyintended to refer to the same implementation and/or embodiment or to anyone particular implementation and/or embodiment. Furthermore, it is tobe understood that particular features, structures, characteristics,and/or the like described are capable of being combined in various waysin one or more implementations and/or embodiments and, therefore, arewithin intended claim scope. However, these and other issues have apotential to vary in a particular context of usage. In other words,throughout the disclosure, particular context of description and/orusage provides helpful guidance regarding reasonable inferences to bedrawn; however, likewise, “in this context” in general without furtherqualification refers to the context of the present disclosure.

To support positioning of a mobile device, two broad classes of locationsolution have been defined: control plane and user plane. With controlplane (CP) location, signaling related to positioning and support ofpositioning may be carried over existing network (and mobile device)interfaces and using existing protocols dedicated to the transfer ofsignaling. With user plane (UP) location, signaling related topositioning and support of positioning may be carried as part of otherdata using such protocols as the Internet Protocol (IP), TransmissionControl Protocol (TCP) and User Datagram Protocol (UDP).

The Third Generation Partnership Project (3GPP) has defined controlplane location solutions for mobile devices that use radio accessaccording to Global System for Mobile communications GSM (2G), UniversalMobile Telecommunications System (UMTS) (3G), Fourth Generation (4G)Long Term Evolution (LTE), and Fifth Generation (5G) New Radio (NR).These solutions are defined in 3GPP Technical Specifications (TSs)23.271 (common part for 2G-4G), 43.059 (GSM access), 25.305 (UMTSaccess), 36.305 (LTE access), and 23.501 and 23.502 (5G access). TheOpen Mobile Alliance (OMA) has similarly defined a UP location solutionknown as Secure User Plane Location (SUPL) which can be used to locate amobile device accessing any of a number of radio interfaces that supportIP packet access such as General Packet Radio Service (GPRS) with GSM,GPRS with UMTS, or IP access with LTE or NR.

Both CP and UP location solutions may employ a location server (LS) tosupport positioning. The LS may be part of or accessible from a servingnetwork or a home network for a user equipment (UE) or may simply beaccessible over the Internet or over a local Intranet. If positioning ofa UE is needed, an LS may initiate a session (e.g. a location session ora SUPL session) with the UE and coordinate location measurements by theUE and determination of an estimated location of the UE. During alocation session, an LS may request positioning capabilities of the UE(or the UE may provide them without a request), may provide assistancedata to the UE (e.g. if requested by the UE or in the absence of arequest) and may request a location estimate or location measurementsfrom a UE, e.g. for the Assisted Global Navigation Satellite System(A-GNSS), Observed Time Difference of Arrival (OTDOA) and/or EnhancedCell ID (ECID) position methods. Assistance data may be used by a UE tohelp acquire and measure signals, such as GNSS signals for A-GNSS and/ora Positioning Reference Signal (PRS) for OTDOA (e.g. by providingexpected characteristics of these signals such as frequency, bandwidth,expected time of arrival, signal coding, signal Doppler).

In a UE based mode of operation, assistance data may also or instead beused by a UE to help determine a location estimate for the UE from theresulting location measurements (e.g., if the assistance data providessatellite ephemeris data in the case of A-GNSS positioning or basestation locations and other base station characteristics such as PRStiming in the case of terrestrial positioning using OTDOA).

In an alternative UE assisted mode of operation, a UE may returnlocation measurements to an LS which may determine an estimated locationof the UE based on these measurements and possibly based also on otherknown or configured data (e.g. satellite ephemeris data for A-GNSSlocation or base station characteristics including base stationlocations and possibly PRS timing in the case of terrestrial positioningusing OTDOA).

In another standalone mode of operation, a UE may make location relatedmeasurements without any positioning assistance data from an LS and mayfurther compute a location or a change in location without anypositioning assistance data from an LS. Position methods that may beused in a standalone mode include GPS and Global Navigation SatelliteSystem (GNSS) (e.g. if a UE obtains satellite orbital data fromnavigation data broadcast by GPS and GNSS satellites themselves) as wellas sensors. It is noted that the terms “positioning assistance data”,“location assistance data” and “assistance data” (AD) are usedsynonymously herein to refer to data which may be provided to a mobiledevice via broadcast or by point to point means to assist the mobiledevice to obtain location measurements (also referred to as positioningmeasurements) and/or to compute a location estimate from positioningmeasurements.

In the case of 3GPP CP location, an LS may be an enhanced serving mobilelocation center (E-SMLC) in the case of LTE access, a standalone SMLC(SAS) in the case of UMTS access, a serving mobile location center(SMLC) in the case of GSM access, or a Location Management Function(LMF) in the case of 5G (e.g. NR) access. In the case of OMA SUPLlocation, an LS may be a SUPL Location Platform (SLP) which may act asany of: (i) a home SLP (H-SLP) if in or associated with the home networkof a UE or if providing a permanent subscription to a UE for locationservices; (ii) a discovered SLP (D-SLP) if in or associated with someother (non-home) network or if not associated with any network; (iii) anEmergency SLP (E-SLP) if supporting location for an emergency callinitiated by the UE; or (iv) a visited SLP (V-SLP) if in or associatedwith a serving network or a current local area for a UE.

During a location session (also referred to as a positioning session),an LS and a UE may exchange messages defined according to somepositioning protocol in order to coordinate the determination of anestimated location for the UE. Possible positioning protocols mayinclude, for example, the LTE Positioning Protocol (LPP) defined by 3GPPin 3GPP TS 36.355 and the LPP Extensions (LPPe) protocol defined by OMAin OMA TSs OMA-TS-LPPe-V1_0, OMA-TS-LPPe-V1_1 and OMA-TS-LPPe-V2_0. TheLPP and LPPe protocols may be used in combination where an LPP messagecontains an embedded LPPe message. The combined LPP and LPPe protocolsmay be referred to as LPP/LPPe. LPP and LPP/LPPe may be used to helpsupport the 3GPP control plane location solution for LTE access, inwhich case LPP or LPP/LPPe messages are exchanged between a UE andE-SMLC. LPP or LPP/LPPe messages may be exchanged between a UE andE-SMLC via a serving Mobility Management Entity (MME) and a servingeNodeB for the UE. LPP and LPP/LPPe may also be used to help support theOMA SUPL solution for many types of wireless access that support IPmessaging (such as LTE, NR and WiFi), where LPP or LPP/LPPe messages areexchanged between a SUPL Enabled Terminal (SET), which is the term usedfor a UE with SUPL, and an SLP, and may be transported within SUPLmessages, such as a SUPL POS or SUPL POS INIT message, which may beconveyed using TCP and IP protocols.

An LS and a base station (e.g. an eNodeB for LTE access) may exchangemessages to enable the LS to (i) obtain position measurements for aparticular UE from the base station, or (ii) obtain location informationfrom the base station not related to a particular UE such as thelocation coordinates of an antenna for the base station, the cells (e.g.cell identities) supported by the base station, cell timing for the basestation and/or parameters for signals transmitted by the base stationsuch as PRS signals. In the case of LTE access, the LPP A (LPPa)protocol defined in 3GPP TS 36.455 may be used to transfer such messagesbetween a base station that is an eNodeB and an LS that is an E-SMLC.

To support low cost UEs and particularly Internet of Things (IoT) UEs,3GPP has defined a variant of LTE, referred to as Narrow Band Internetof Things (NB-IoT), which provides a UE with access to a single LTEresource block, comprising 200 KHz total bandwidth and 180 KHz of usablebandwidth, for signaling and data use. Support and usage of NB-IoT isintended mainly for UEs which are not associated with a human user, butinstead are used for such applications as telemetry, asset tracking (andchild and pet tracking), utility meter reporting, vending machines,safety and security monitoring etc. and which are typically part of IoT.Such UEs may often be low cost and can be powered by (e.g.non-rechargeable) batteries with an expected lifetime of up to tenyears. As a consequence, it may be desirable or necessary to employminimal hardware capability and consume minimal power, which may lead tomany or most such UEs having only one radio receiver (RF chain).Consequently, such a UE may not be able to obtain location measurementsfor non-NB-IoT radio signals such as GNSS or Wireless Local Area Network(WLAN) signals when in an NB-IoT connected state, and measurements ofNB-IoT radio signals may also be problematic, due to dedication of thesingle RF chain only to signaling and data transfer with a wireless(NB-IoT) network.

To enable location measurements by a UE with only one RF chain, the UEmay enter an idle state to obtain the location measurements, after whichthe UE may re-enter a connected state and send the measurements to thelocation server. For an SLP location server, using the SUPL user planelocation solution, however, the SLP may not be aware that the UE hasNB-IoT access, which may lead to communication problems between the UEand SLP while the UE is in an idle state. For example, the SLP may senda request to the UE for additional location measurements or for thelocation capabilities of the UE and may expect a response from the UEwithin some limited time (e.g. 20 seconds or less), or at least mayexpect an acknowledgment of the request (e.g., at the TCP level) fromthe UE. The lack of a response or lack of an acknowledgment from the UEwithin some minimum time (e.g., 20 seconds or less) may cause the SLP toabort the location session in some implementations. In otherimplementations, the entry into an idle state by the UE may cause a TCPconnection between the UE and SLP to disconnect due to lack of responsesto TCP keep alive messages and failure of TCP retransmission. This couldlead to a failure to locate the UE.

A solution to the above-identified problem for SUPL may include, e.g.,providing an indication from the UE to the SLP that the UE is about toenter an idle state in order to obtain requested location measurements.The SUPL location session may then be released, e.g., by the SLP or theUE. After the UE obtains the location measurements while in the idlestate, the UE may reconnect to the SLP and a new SUPL location sessionmay be initiated (e.g. by the UE or by the SLP), in which the UE mayprovide the requested location measurements to the SLP. The new SUPLlocation session, for example, may be a copy of the first SUPL locationsession, e.g., using the same identification information, to avoidaccidental association with some other non-related SUPL session.

FIG. 1 is a diagram illustrating a communication system 100 for locationsupport of a user equipment (UE) 105 that supports and is currentlyusing LTE radio access (also referred to as wideband LTE) or Narrow BandInternet of Things (NB-IoT) radio access (also referred to as narrowbandLTE), where NB-IoT and LTE may be as defined by 3GPP—e.g. in 3GPP TS36.300. The communication system 100 may be referred to as an EvolvedPacket System (EPS). As illustrated, the communication system 100 mayinclude the UE 105, an Evolved Universal Mobile TelecommunicationsService (UMTS) Terrestrial Radio Access (E-UTRA) Network (E-UTRAN) 112,and an Evolved Packet Core (EPC) 120. The E-UTRAN 112 and the EPC 120may be part of a Visited Public Land Mobile Network (VPLMN) that is aserving network for the UE 105 and communicates with a Home Public LandMobile Network (HPLMN) for the UE 105 (not shown in FIG. 1) or may bepart of the HPLMN for UE 105. The E-UTRAN 112 and EPC 120 mayinterconnect with other networks. For example, the Internet may be usedto carry messages to and from different networks or between differententities within a network, such as between the Packet Data NetworkGateway (PDG) 128 that may be connected to the Serving Gateway (SGW)126. For simplicity these networks and associated entities andinterfaces are not shown. As shown, the communication system 100provides packet-switched services to the UE 105. However, as thoseskilled in the art will readily appreciate, the various conceptspresented throughout this disclosure may be extended to networksproviding circuit-switched services.

The UE 105 may comprise any electronic device configured for NB-IoTand/or LTE radio access, for example. The UE 105 may be referred to as adevice, a wireless device, a mobile terminal, a terminal, a mobilestation (MS), a mobile device, a SUPL Enabled Terminal (SET), or by someother name and may correspond to (or be part of) a smart watch, digitalglasses, fitness monitor, smart car, smart appliance, cellphone,smartphone, laptop, tablet, PDA, tracking device, control device, orsome other portable or moveable device. A UE 105 may comprise a singleentity or may comprise multiple entities such as in a personal areanetwork where a user may employ audio, video and/or data I/O devicesand/or body sensors and a separate wireline or wireless modem.Typically, though not necessarily, a UE 105 may support wirelesscommunication with one or more types of Wireless Wide Area Network(WWAN) such as a WWAN supporting Global System for Mobile Communications(GSM), Code Division Multiple Access (CDMA), Wideband CDMA (WCDMA), LongTerm Evolution (LTE), Narrow Band Internet of Things (NB-IoT), EnhancedMachine Type Communications (eMTC) also referred to as LTE category M1(LTE-M), High Rate Packet Data (HRPD), 5G New Radio (NR), WiMax, etc.EPC 120 combined with E-UTRAN 112 may be an example of a WWAN. A UE 105may also support wireless communication with one or more types ofWireless Local Area Network (WLAN) such as a WLAN supporting IEEE 802.11WiFi (also referred to as Wi-Fi) or Bluetooth® (BT). UE 105 may alsosupport communication with one or more types of wireline network such asby using a Digital Subscriber Line (DSL) or packet cable for example.Although FIG. 1 shows only one UE 105, there may be many other UEs (e.g.hundreds, thousands or millions) that can each correspond to UE 105.Typically, the UE 105 has a single radio receiver (RF chain) whichprevents or impedes location measurements by the UE 105 when in aconnected state with the EPS in communication system 100.

The UE 105 may enter a connected state with a wireless communicationnetwork that may include the E-UTRAN 112 and EPC 120. In one example, UE105 may communicate with a cellular communication network bytransmitting wireless signals to, and/or receiving wireless signalsfrom, a cellular transceiver, such as an evolved Node B (eNodeB or eNB)110-1 in the E-UTRAN 112. The E-UTRAN 112 may include one or moreadditional eNBs 110-2. The eNB 110-1 provides user plane and controlplane protocol terminations toward the UE 105. The eNB 110-1 maycomprise a serving eNB for UE 105 and may also be referred to as a basestation, a base transceiver station, a radio base station, a radiotransceiver, a radio network controller, a transceiver function, a basestation subsystem (BSS), an extended service set (ESS), or by some othersuitable terminology. The UE 105 also may transmit wireless signals to,or receive wireless signals from, a local transceiver (not shown in FIG.1), such as an access point (AP), femtocell, Home Base Station, smallcell base station, Home Node B (HNB) or Home eNodeB (HeNB), which mayprovide access to a wireless local area network (WLAN, e.g., IEEE 802.11network), a wireless personal area network (WPAN, e.g., Bluetoothnetwork) or a cellular network (e.g. an LTE network or other wirelesswide area network such as those discussed in the next paragraph). Ofcourse, it should be understood that these are merely examples ofnetworks that may communicate with a mobile device over a wireless link,and claimed subject matter is not limited in this respect.

Examples of network technologies that may support wireless communicationinclude NB-IoT and LTE, but may further include GSM, CDMA, WCDMA, HRPD,eMTC and 5G NR. NB-IoT, GSM, WCDMA, LTE, eMTC and NR are technologiesdefined by 3GPP. CDMA and HRPD are technologies defined by the 3rdGeneration Partnership Project 2 (3GPP2). Cellular transceivers, such aseNBs 110-1 and 110-2, may comprise deployments of equipment providingsubscriber access to a wireless telecommunication network for a service(e.g., under a service contract). Here, a cellular transceiver mayperform functions of a cellular base station in servicing subscriberdevices within a cell determined based, at least in part, on a range atwhich the cellular transceiver is capable of providing access service.

The eNBs 110-1 and 110-2 may be connected by an interface (e.g. the 3GPPSi interface) to the EPC 120. The EPC 120 includes a Mobility ManagementEntity (MME) 122, and a Serving Gateway (SGW) 126 through which data(e.g. Internet Protocol (IP) packets) to and from the UE 105 may betransferred. The MME 122 may be the serving MME for UE 105 and is thenthe control node that processes the signaling between the UE 105 and theEPC 120 and supports attachment and network connection of UE 105,mobility of UE 105 (e.g. via handover between network cells) as well asestablishing and releasing data bearers on behalf of the UE 105.Generally, the MME 122 provides bearer and connection management for theUE 105 and may be connected to the SGW 126, the eNBs 110-1 and 110-2, anEnhanced Serving Mobile Location Center (E-SMLC) 124 and a GatewayMobile Location Center (GMLC) 132 in the EPC 120.

The E-SMLC 124 may support location of the UE 105 using the 3GPP controlplane (CP) location solution defined in 3GPP technical specifications(TSs) 23.271 and 36.305. The GMLC 132 may provide access on behalf of anexternal client (e.g. external client 150) or another network (e.g.HPLMN) to the location of UE 105. The external client 150 may comprise aweb server or remote application that may have some association with UE105 (e.g. may be accessed by a user of UE 105 via E-UTRAN 112 and EPC120) or may be a server, application or computer system providing alocation service to some other user or users which may include obtainingand providing the location of UE 105 (e.g. to enable a service such asfriend or relative finder, asset tracking or child or pet location). Theexternal client 150 may be referred to as a SUPL Agent 150 whenaccessing an SLP such as SLP 130.

E-SMLC 124 may be connected to or have access to one or more referencestations 135 which may be part of EPC 120 or separate from EPC 120 (e.g.part of a GNSS reference network and owned and operated by a serviceprovider different to the operator of EPC 120). A reference station 135may comprise or include a GNSS receiver configured to acquire, measureand decode signals transmitted by one or more GNSSs. A reference station135 may be configured to obtain or determine orbital and timing data forSatellite Vehicles (SVs) 160 for one or more GNSSs and infer informationfor environmental factors that can affect GNSS location such asionospheric and tropospheric delay. A reference station 135 may transferdetermined information to E-SMLC 124—e.g. periodically or whenever thedetermined information changes.

As illustrated, the EPC 120 includes a Packet Data Network Gateway (PDG)128 that may be connected to the SGW 126 (e.g. via the Internet,directly or through a local intranet). The PDG 128 may provide UE 105with Internet Protocol (IP) address allocation and IP and other dataaccess to external networks (e.g. the Internet) and to external clients(e.g. external client 150) and external servers, as well as other datatransfer related functions. In some cases, PDG 128 may be located in anHPLMN and not in EPC 120 when the UE 105 is roaming and receives localIP breakout. The PDG 128 may be connected to a location server, such asSLP 130. The SLP 130 may support the SUPL UP location solution definedby OMA and may support location services for UE 105 based onsubscription information for UE 105 stored in SLP 130.

In some embodiments of communication system 100, SLP 130 may function asa Home SLP (H-SLP) for UE 105, a Discovered SLP (D-SLP) and/or as anEmergency SLP (E-SLP).

To support a SUPL location session (also referred to as a SUPL session,a SUPL positioning session or a location session) between UE 105 and SLP130 in communication system 100, the UE 105 and SLP 130 may exchangeSUPL messages at a user plane level using IP and TCP (or possibly UDPfor an initial SUPL INIT message) as transport protocols. FIG. 1 shows atypical path 170 for a SUPL message, which comprises routing the SUPLmessage through eNB 110-1, SGW 126 and PDG 128, in this order for a SUPLmessage sent from UE 105 to SLP 130 or in the reverse order for a SUPLmessage sent from SLP 130 to UE 105. For example, in the signaling flowsdescribed later for FIGS. 3-6, each of the SUPL messages shown as beingtransferred between the UE 105 and SLP 130 may be transferred viarouting along the path 170, when the signaling flows are supported bycommunication system 100.

The GMLC 132 may be connected to a Home Subscriber Server (HSS) 134 forUE 105, which is a central database that contains user-related andsubscription-related information for UE 105. The GMLC 132 may providelocation access to the UE 105 on behalf of external clients such asexternal client 150. The EPC 120 may further include a LocationRetrieval Function (LRF) 136 that may be connected to the GMLC 132and/or to the SLP 130, as defined in 3GPP Technical Specifications (TSs)23.271 and 23.167. LRF 136 may perform the same or similar functions toGMLC 132, with respect to receiving and responding to a location requestfrom an external client 150 that corresponds to a Public SafetyAnswering Point (PSAP) supporting an emergency call from UE 105. One ormore of the GMLC 132, PDG 128, LRF 136, and SLP 130 may be connected tothe external client 150, e.g., through another network, such as theInternet. In some cases, a Requesting GMLC (RGMLC) located in anotherPLMN (not shown in FIG. 1) may be connected to GMLC 132 (e.g. via theInternet) and/or to the SLP 130 in order to provide location access toUE 105 on behalf of external clients connected to the RGMLC. The GMLC132 may support location access to the UE 105 using the 3GPP CP solutiondefined in 3GPP TS 23.271.

It should be understood that while a single network (comprising E-UTRAN112 and EPC 120) is illustrated in FIG. 1, a separate HPLMN may bepresent, which may include a separate GMLC (e.g., an H-GMLC) and mayinclude the SLP 130 (e.g. connected to a PDG in the HPLMN, where the PDGmay be connected to the SGW 126 in EPC 120).

In particular implementations, the UE 105 may have circuitry andprocessing resources capable of obtaining location related measurements(also referred to as location measurements), such as measurements forsignals received from GPS or other Satellite Positioning System (SPS)SVs 160, measurements for cellular transceivers such as eNBs 110-1 and110-2, and/or measurements for local transceivers. UE 105 may furtherhave circuitry and processing resources capable of computing a positionfix or estimated location of UE 105 based on these location relatedmeasurements. In some implementations, location related measurementsobtained by UE 105 may be transferred to a location server, such as theE-SMLC 124, or SLP 130, after which the location server may estimate ordetermine a location for UE 105 based on the measurements.

Location related measurements obtained by UE 105 may includemeasurements of signals received from SVs 160 that are part of an SPS orGlobal Navigation Satellite System (GNSS) such as GPS, GLONASS, Galileoor Beidou and/or may include measurements of signals received fromterrestrial transmitters fixed at known locations (e.g., such as eNB110-1, eNB 110-2 or other local transceivers). UE 105 or a separatelocation server (e.g. E-SMLC 124 or SLP 130) may then obtain a locationestimate for the UE 105 based on these location related measurementsusing any one of several position methods such as, for example, GNSS,Assisted GNSS (A-GNSS), Advanced Forward Link Trilateration (AFLT),Observed Time Difference Of Arrival (OTDOA), Enhanced Cell ID (ECID),WiFi (also referred to as WLAN positioning), or combinations thereof. Insome of these techniques (e.g. A-GNSS, AFLT and OTDOA), pseudoranges,code phases, carrier phases or timing differences may be measured by UE105 relative to three or more terrestrial transmitters fixed at knownlocations or relative to four or more SVs with accurately known orbitaldata, or combinations thereof, based at least in part, on pilot signals,positioning reference signals (PRS) or other positioning related signalstransmitted by the transmitters or SVs and received at the UE 105. Here,location servers, such as E-SMLC 124 or SLP 130, may be capable ofproviding positioning assistance data to UE 105 including, for example,information regarding signals to be measured by UE 105 (e.g., expectedsignal timing, signal coding, signal frequencies, signal Doppler),locations and/or identities of terrestrial transmitters, and/or signal,timing and orbital information for GNSS SVs 160 to facilitatepositioning techniques such as A-GNSS, AFLT, OTDOA and ECID. Thefacilitation may include improving signal acquisition and measurementaccuracy by UE 105 and/or, in some cases, enabling UE 105 to compute itsestimated location based on the location measurements. For example, alocation server may comprise an almanac (e.g., a Base Station Almanac(BSA)) which indicates the locations and identities of cellulartransceivers and transmitters (e.g. eNBs 110-1 and 110-2) and/or localtransceivers and transmitters in a particular region or regions such asa particular venue, and may further contain information descriptive ofsignals transmitted by these transceivers and transmitters such assignal power, signal timing, signal bandwidth, signal coding and/orsignal frequency. In the case of ECID, a UE 105 may obtain measurementsof signal strength (e.g. received signal strength indication (RSSI) orreference signal received power (RSRP)) for signals received fromcellular transceivers (e.g., eNBs 110-1, 110-2) and/or localtransceivers and/or may obtain a signal to noise ratio (S/N), areference signal received quality (RSRQ), or a round trip signalpropagation time (RTT) between UE 105 and a cellular transceiver (e.g.,eNB 110-1 or 110-2) or a local transceiver. A UE 105 may transfer thesemeasurements to a location server, such as E-SMLC 124 or SLP 130, todetermine a location for UE 105, or in some implementations, UE 105 mayuse these measurements together with positioning assistance data (e.g.terrestrial almanac data or GNSS SV data such as GNSS Almanac and/orGNSS Ephemeris information) received from the location server todetermine a location for UE 105.

In the case of OTDOA, UE 105 may measure a Reference Signal TimeDifference (RSTD) between signals, such as a Position Reference Signal(PRS) or Cell Specific Reference Signal (CRS), received from nearbytransceivers or base stations (e.g. eNBs 110-1 and 110-2). An RSTDmeasurement may provide the time of arrival difference between signals(e.g. CRS or PRS) received at UE 105 from two different transceivers(e.g. an RSTD between signals received from eNB 110-1 and from eNB110-2). The UE 105 may return the measured RSTDs to a location server(e.g. E-SMLC 124 or SLP 130), which may compute an estimated locationfor UE 105 based on known locations and known signal timing for themeasured transceivers. In some implementations of OTDOA, the signalsused for RSTD measurements (e.g. PRS or CRS signals) may be accuratelysynchronized by the transceivers or transmitters to a common universaltime such as GPS time or coordinated universal time (UTC), e.g., using aGPS receiver at each transceiver or transmitter to accurately obtain thecommon universal time.

An estimate of a location of a UE 105 may be referred to as a location,location estimate, location fix, fix, position, position estimate orposition fix, and may be geodetic, thereby providing locationcoordinates for the UE 105 (e.g., latitude and longitude) which may ormay not include an altitude component (e.g., height above sea level,height above or depth below ground level, floor level or basementlevel). Alternatively, a location of the UE 105 may be expressed as acivic location (e.g., as a postal address or the designation of somepoint or small area in a building such as a particular room or floor). Alocation of a UE 105 may also include an uncertainty and may then beexpressed as an area or volume (defined either geodetically or in civicform) within which the UE 105 is expected to be located with some givenor default probability or confidence level (e.g., 67% or 95%). Alocation of a UE 105 may further be an absolute location (e.g. definedin terms of a latitude, longitude and possibly altitude and/oruncertainty) or may be a relative location comprising, for example, adistance and direction or relative X, Y (and Z) coordinates definedrelative to some origin at a known absolute location or some previouslocation of UE 105. In the description contained herein, the use of theterm location may comprise any of these variants unless indicatedotherwise. Measurements (e.g. obtained by UE 105 or by another entitysuch as eNB 110-1) that are used to determine (e.g. calculate) alocation estimate for UE 105 may be referred to as measurements,location measurements, location related measurements, positioningmeasurements or position measurements and the act of determining alocation for the UE 105 may be referred to as positioning of the UE 105or locating the UE 105.

According to an embodiment, communication system 100 may be configuredto deliver positioning assistance data in downlink broadcast messages toUE devices such as UE 105. For example, positioning assistance data maybe broadcasted in system information blocks (SIBs) in downlink messagesfrom eNB devices 110-1 and 110-2. Furthermore, positioning assistancedata that is broadcasted in the SIBs may be key encrypted (also referredto as being ciphered). UE 105 may receive one or more cipher keys inmessages other than the broadcast messages for use in decrypting thebroadcasted positioning assistance data.

FIG. 2 shows a diagram of a communication system 200, according to analternative embodiment to the embodiment of communication system 100described above with reference to FIG. 1. In communication system 200,UE 105, SVs 160 and external client 150 may operate in connection withFifth Generation (5G) features of communication system 200. Here, thecommunication system 200 comprises a UE 105, and components of a FifthGeneration (5G) network, comprising a Next Generation RAN (NG-RAN) 212and a 5G Core Network (5GCN) 250. NG-RAN 212 plus 5GCN 250 may comprisea 5G System (5GS) (also referred to as 5G network) which may function asa VPLMN or an HPLMN for UE 105. When functioning as a VPLMN, there maybe a separate HPLMN for the UE 105 (not shown in FIG. 2) thatcommunicates with the 5GCN 250 (e.g. via the Internet). Thecommunication system 200 may further utilize information from satellitevehicles (SVs) 160 for a Global Navigation Satellite System (GNSS) likethe Global Positioning System (GPS), GLONASS, Galileo, Beidou or someother local or regional Satellite Positioning System (SPS) such asIRNSS, EGNOS or WAAS. Additional components of the communication system200 are described below. The communication system 200 may includeadditional or alternative components.

It should be noted that FIG. 2 provides only a generalized illustrationof various components, any or all of which may be utilized asappropriate, and each of which may be duplicated or omitted asnecessary. Specifically, although only one UE 105 is illustrated, itwill be understood that many UEs (e.g., hundreds, thousands, millions,etc.) may utilize the communication system 200. Similarly, thecommunication system 200 may include a larger or smaller number of SVs160, gNBs 210, external clients 150, and/or other components. Theillustrated connections that connect the various components in thecommunication system 200 include data and signaling connections whichmay include additional (intermediary) components, direct or indirectphysical and/or wireless connections, and/or additional networks.Furthermore, components may be rearranged, combined, separated,substituted, and/or omitted, depending on desired functionality.

While FIG. 2 illustrates a 5G network, similar network implementationsand configurations may be used for other communication technologies,such as 3G, Long Term Evolution (LTE), IEEE 802.11 WiFi (also referredto as Wi-Fi) etc.

Base stations (BSs) in the NG-RAN 212 shown in FIG. 2 comprise NR NodeBs, also referred to as gNBs, 210-1, 210-2 and 210-3 (collectively andgenerically referred to herein as gNBs 210). Pairs of gNBs 210 in NG-RAN212 may be connected to one another—e.g. directly as shown in FIG. 2 orindirectly via other gNBs 210. Access to the 5G network is provided toUE 105 via wireless communication between the UE 105 and one or more ofthe gNBs 210, which may provide wireless communication access to the5GCN 250 on behalf of the UE 105 using 5G NR. In FIG. 2, the serving gNBfor UE 105 is assumed to be gNB 210-1, although other gNBs (e.g. gNB210-2 and/or gNB 210-3) may act as a serving gNB if UE 105 moves toanother location or may act as a secondary gNB to provide additionalthroughout and bandwidth to UE 105. Some gNBs 210 in FIG. 2 (e.g. gNB210-2 or gNB 210-3) may be configured to function as positioning-onlybeacons which may transmit signals (e.g. a Positioning Reference Signal(PRS)) to assist positioning of UE 105 but may not receive signals fromUE 105 or from other UEs.

As noted, while FIG. 2 depicts nodes configured to communicate accordingto 5G communication protocols, nodes configured to communicate accordingto other communication protocols, such as, for example, the LTE protocolor IEEE 801.11 WiFi, may be used. Such nodes, configured to communicateusing different protocols, may be controlled, at least in part, by the5GCN 250. Thus, the NG-RAN 212 may include any combination of gNBs,evolved Node Bs (eNBs) supporting LTE access, or other types of basestations or access points. As an example, NG-RAN 212 may include one ormore next generation eNBs (ng-eNBs) which provide LTE wireless access toUE 105 and which may connect to gNBs 210 in NG-RAN 212 and/or toentities in 5GCN 250 such as an Access and Mobility Management Function(AMF) 254 and a User Plane Function (UPF) 257.

The gNBs 210 can communicate with the AMF 254, which, for positioningfunctionality, communicates with a Location Management Function (LMF)252. The AMF 254 may support access and registration by the UE 105,mobility of the UE 105, including cell change and handover and mayparticipate in supporting a signaling connection to the UE 105 andpossibly helping establish and release Protocol Data Unit (PDU) sessionsfor UE 105. Other functions of AMF 254 may include: termination of acontrol plane (CP) interface from NG-RAN 212; termination of Non-AccessStratum (NAS) signaling connections from UEs such as UE 105; NASciphering and integrity protection; registration management; connectionmanagement; reachability management; mobility management; transport ofShort Message Service (SMS) messages between UE 105 and an SMS Function(SMSF) (not shown in FIG. 2); access authentication and authorization.

The LMF 252 may support positioning of the UE 105 when UE 105 accessesthe NG-RAN 212 and may support position procedures/methods such asAssisted GNSS (A-GNSS), Observed Time Difference of Arrival (OTDOA),Real Time Kinematics (RTK), Precise Point Positioning (PPP),Differential GNSS (DGNSS), Enhanced Cell ID (ECID), angle of arrival(AOA), angle of departure (AOD), round trip signal propagation time(RTT), WLAN positioning and/or other position methods.

The LMF 252 may also process location services requests for the UE 105,e.g., received from the AMF 254. In some embodiments, a node/system thatimplements the LMF 252 may additionally or alternatively implement othertypes of location-support modules, such as an Enhanced Serving MobileLocation Center (E-SMLC) or a Secure User Plane Location (SUPL) LocationPlatform (SLP). It is noted that in some embodiments, at least part ofthe positioning functionality (including derivation of the location ofUE 105) may be performed at the UE 105 (e.g., using signal measurementsobtained by UE 105 for signals transmitted by wireless nodes such asgNBs 210, and assistance data provided to the UE 105, e.g. by LMF 252).

The GMLC 255 may support a location request for the UE 105 received froman external client 150 or from a Home GMLC (HGMLC), not shown, and mayforward such a location request to the AMF 254 for forwarding by the AMF254 to the LMF 252 or may forward the location request directly to theLMF 252. A location response from the LMF 252 (e.g. containing alocation estimate for the UE 105) may be similarly returned to GMLC 255either directly or via the AMF 254 and the GMLC 255 may then return thelocation response (e.g., containing the location estimate) to theexternal client 150 or to a HGMLC. The GMLC 255 is shown connected toboth the AMF 254 and LMF 252, but only one of these connections may besupported by 5GCN 250 in some implementations.

A Location Retrieval Function (LRF) 253 may be connected to the GMLC255, as defined in 3GPP Technical Specification (TS) 23.271. LRF 253 mayperform the same or similar functions to GMLC 255, with respect toreceiving and responding to a location request from an external client150 that corresponds to a Public Safety Answering Point (PSAP)supporting an emergency call from UE 105.

The LMF 252 and the gNBs 210 may communicate using a New Radio PositionProtocol A (NRPPa), defined in 3GPP Technical Specification (TS) 38.455,with NRPPa messages being transferred between the gNBs 210 and the LMF252 via the AMF 254. The LMF 252 and UE 105 may communicate using theLTE Positioning Protocol (LPP) defined in 3GPP TS 36.355, where LPPmessages are transferred inside NAS transport messages between the UE105 and the AMF 254 via a serving gNB 210-1 for UE 105, and where AMF254 relays the LPP messages to and from LMF 252. The LPP protocol may beused to support positioning of UE 105 using UE assisted and/or UE basedposition methods such as A-GNSS, RTK, OTDOA, ECID and/or WLANpositioning. The NRPPa protocol may be used to support positioning of UE105 using network based position methods such as ECID (e.g. when usedwith measurements obtained by a gNB 210 of signals transmitted by UE105) and/or may be used by LMF 252 to obtain location relatedinformation from gNBs 210. For example, location related informationprovided by the gNBs 210 to the LMF 252 using NRPPa may include timingand configuration information for PRS transmission from gNBs 210 and/orlocation coordinates of the gNBs 210. The LMF 252 can then provide someor all of this location related information to the UE 105 as assistancedata in an LPP message via the NG-RAN 212 and the 5GCN 250.

An LPP message sent from the LMF 252 to the UE 105 may instruct the UE105 to do any of a variety of things, depending on desiredfunctionality. For example, the LPP message could contain an instructionfor the UE 105 to obtain measurements for GNSS (or A-GNSS), WLAN, and/orOTDOA (or some other position method). In the case of OTDOA, the LPPmessage may instruct the UE 105 to obtain one or more measurements (e.g.RSTD measurements) of PRS signals transmitted within particular cellssupported by particular gNBs 210 (or supported by one or more ng-eNBs oreNBs). The UE 105 may send the measurements back to the LMF 252 in anLPP message (e.g. inside a 5G NAS message) via the serving gNB 210-1 andthe AMF 254.

In some embodiments, LPP may be augmented by or replaced by an NRpositioning protocol (NPP or NRPP) which supports position methods suchas OTDOA and ECID for NR radio access. For example, an LPP message maycontain an embedded NPP message or may be replaced by an NPP message.

As illustrated, 5GCN 250 includes a Unified Data Management (UDM) 242that may be connected to the GMLC 255 (e.g., via the Internet), as wellas a User Plane Function (UPF) 257. The UDM 242 is analogous to a HomeSubscriber Server (HSS) for LTE access, and if desired, the UDM 242 maybe combined with an HSS. The UDM 242 is a central database that containsuser-related and subscription related information for UE 105 and mayperform the following functions: UE authentication, UE identification,access authorization, registration and mobility management, subscriptionmanagement and SMS management. The UPF 257 may support voice and databearers for UE 105 and may enable UE 105 voice and data access to othernetworks such as the Internet. UPF functions may include: external PDUsession point of interconnect to a Data Network, packet (e.g. InternetProtocol (IP)) routing and forwarding, packet inspection and user planepart of policy rule enforcement, Quality of Service (QoS) handling foruser plane, downlink packet buffering and downlink data notificationtriggering.

The UPF 257 may be connected to a location server (LS), such as the SLP130. The SLP 130 may support the SUPL user plane (UP) location solutiondefined by the Open Mobile Alliance (OMA) and may support locationservices for UE 105 based on subscription information for UE 105 storedin SLP 130. The SLP 130 may function as a home SLP (SLP) for UE 105, aDiscovered SLP (D-SLP) and/or as an Emergency SLP (E-SLP) (not shown inFIG. 2). SLP 130 and LMF 252 in communication system 200 are bothexamples of an LS that may employ the LPP and/or LPP/LPPe protocols forpositioning of UE 105.

To support a SUPL location session between UE 105 and SLP 130 incommunication system 200, the UE 105 and SLP 130 may exchange SUPLmessages at a user plane level using IP and TCP (or possibly UDP for aninitial SUPL INIT message) as transport protocols. FIG. 2 shows atypical path 270 for a SUPL message, which comprises routing the SUPLmessage through gNB 210-1 and UPF 257, in this order for a SUPL messagesent from UE 105 to SLP 130 or in the reverse order for a SUPL messagesent from SLP 130 to UE 105. For example, in the signaling flowsdescribed later for FIGS. 3-6, each of the SUPL messages shown as beingtransferred between the UE 105 and SLP 130 may be transferred viarouting along the path 270, when the signaling flows are supported bycommunication system 200.

The GMLC 255 may be connected to UDM 242 for UE 105. One or more of GMLC255, UPF 257, LRF 253 and SLP 130 may be connected to external client150, e.g., through another network, such as the Internet. In some cases,a Requesting GMLC (RGMLC) located in another PLMN (not shown in FIG. 2)may be connected to GMLC 255 (e.g., via the Internet) in order toprovide location access to UE 105 on behalf of external clientsconnected to the RGMLC. The RGMLC and GMLC 255 may support locationaccess to UE 105 using the 3GPP CP solution defined in 3GPP TS 23.271and in 3GPP TS 23.501 and 3GPP TS 23.502.

It should be understood that while a single network (comprising NG-RAN212 and 5GCN 250) is illustrated in FIG. 2, a separate HPLMN may bepresent, which may include a separate GMLC, a separate LRF a separateUPF, and may include the SLP 130 (e.g. connected to the separate UPF).

While communication system 200 is described as supporting NR wirelessaccess (via gNBs 210) and/or LTE wireless access (via ng-eNBs in NG-RAN212), future releases of 3GPP specifications may define a capability tosupport NB-IoT wireless access to NG-RAN 212 and 5GCN 250 via ng-eNBs inNG-RAN 212 and/or a narrowband version of NR wireless access via gNBs210 in NG-RAN 212. In such a case, problems with support of locationusing SUPL for NB-IoT wireless access to an EPS such as the EPS forcommunication system 100 may apply similarly or equally to NB-IoT ornarrowband NR wireless access by a UE 105 to NG-RAN 212 and 5GCN 150.

For Narrow Band Internet of Things (NB-IoT) wireless access (andpossibly for a future narrowband version of NR), it is expected thatmany or most UEs will have only one radio receiver (RF chain) to reducecost and power (battery) usage. A consequence for location of such a UEis that the UE may not be able to obtain location measurements fornon-NB-IoT radio signals such as GNSS or WLAN signals when in an NB-IoTconnected state.

In addition, even measurements of NB-IoT radio signals could beproblematic. This problem has been anticipated by 3GPP standards forcontrol plane location, which allow an NB-IoT UE 105 to enter idle stateafter being requested to provide location measurements by a locationserver (e.g. E-SMLC 124 in communication system 100). After entering anidle state, the UE 105 may obtain the measurements, re-enter connectedstate and send the measurements to the location server (e.g. E-SMLC124). The location server may be aware (e.g. from information providedby a serving MME 122) that UE 105 has NB-IoT access. This may allow thelocation server to assign a longer maximum response time to the UE 105when requesting location measurements which can avoid the locationserver timing out on a response from the UE 105. However, for an SLPlocation server, such as SLP 130, using the SUPL user plane locationsolution, the SLP 130 may not be aware that the UE 105 has NB-IoT access(e.g. since no interface has been defined by OMA or 3GPP between an SLPand an MME 122 or AMF 254 which could allow the MME 122 or AMF 254 toinform the SLP that a UE 105 has NB-IoT access). In addition, even if anSLP 130 was aware of NB-IoT access by a UE 105, the entry of the UE 105into an idle state could cause a TCP connection between the UE 105 andSLP 130 to disconnect due to lack of responses to TCP keep alivemessages and/or failure of TCP retransmission. This could lead to afailure to locate the UE 105.

As discussed herein, a solution to the above-identified problem mayinclude, e.g., a first step in which the UE 105 indicates to the SLP 130that the UE 105 is about to enter idle state in order to obtainrequested location measurements. The indication may be carried in a SUPLmessage (e.g. SUPL POS or SUPL END message) or in an LPP message (e.g.an LPP Provide Location Information (PLI) message). The indication, insome embodiments, may be encoded as a parameter, flag, cause value orerror cause value (e.g. an LPP or SUPL error cause value) in an LPP orSUPL message. For example, in one embodiment, the indication maycomprise a new value for a SUPL Status Code parameter which may beincluded in a SUPL END message. In another embodiment, the indicationmay comprise a new value for a “LocationError” parameter which may beincluded in an LPP PLI message.

Additionally, in a second step, the SLP 130 or the UE 105 may releasethe SUPL session, if it is not already released. Following, a short timeperiod (e.g. 30-120 seconds) to allow the UE 130 to enter idle state andobtain location measurements, the UE 105 or SLP 130 may initiate a newSUPL session in which the UE 105 provides the location measurements tothe SLP 130 (e.g. in an LPP PLI message carried in a SUPL POS INITmessage). The SLP 130 may then determine a location for the UE 105,which is returned to the UE 105, e.g., when the first session was UEinitiated, or to an external client 150, e.g., for an SLP initiatedfirst session.

The new SUPL session may be a copy of the first SUPL session and may beinitiated by the same end that initiated the first SUPL session (i.e.,by the UE 105 for a UE initiated first session or by the SLP 130 for anSLP initiated first session), or by a different end (i.e., by the UE 105for an SLP initiated first session or by the SLP 130 for a UE initiatedfirst session). This may allow the same identification information to beused for both SUPL sessions (e.g., the same SUPL Application ID for a UEinitiated first session or the same SUPL Notification parameter for anSLP initiated first session), which can allow the non-initiating end toverify that the second SUPL session is a continuation of the first SUPLsession (and thereby avoid accidental association of the second SUPLsession with a first SUPL session that is for a different externalclient or for a different location application in the UE 105).

FIGS. 3 and 4 show a signaling flow illustrating a process ofdetermining a location for a UE 105 during which the UE 105 enters anidle state to obtain location for a Network Initiated SUPL session. Thesignaling flow in FIGS. 3 and 4 may be applicable to the UE 105 and SLP130 in communication system 100 (e.g. when UE 105 has NB-IoT wirelessaccess to eNB 110) or may be applicable to the UE 105 and SLP 130 incommunication system 200 (e.g. when UE 105 has NB-IoT wireless access toan ng-eNB in NG-RAN 212 or has a future narrowband NR wireless access togNB 210-1). FIG. 3, for example, illustrates the initiation andtermination of an initial positioning session when location is initiatedby SLP 130. As illustrated, at stage A in FIG. 3, a SUPL Agent 150,corresponding to the external client 150 illustrated in FIGS. 1 and 2,sends a location request for the UE 105 to the SLP 130. The locationrequest may be, e.g., an OMA Mobile Location Protocol (MLP) StandardLocation Immediate Request (SLIR) message, which may include, e.g.,identifiers for the UE 105 and the SUPL agent 150.

At stage B, the SLP 130 may authenticate the SUPL Agent 150 and check ifthe SUPL Agent 150 is authorized for the service it requests and mayapply subscriber privacy for UE 105, based on the identifiers itreceived at stage A.

At stage C, the SLP 130 initiates a SUPL positioning session with the UE105 by sending a SUPL INIT message to UE 105 (e.g. using SMS or UDP overIP). The SUPL INIT message contains a session-id (also referred to as asession ID), and may include a Notification parameter and may furtherinclude reasons for the location request, a proxy/non-proxy modeindicator and an intended positioning method.

At stage D, the UE 105 analyses the received SUPL INIT. If found to benon-authentic the UE 105 takes no further action. Otherwise, the UE 105establishes or resumes a secure data connection with the SLP 130, e.g.using TCP and Transport Layer Security (TLS) protocols over IP. Thesecure data connection may then be used to transport further SUPLmessages at stages E-L.

At stage E, the UE 105 sends a SUPL POS INIT message to the SLP 130. TheSUPL POS INIT message may contain, e.g., a session-id, UE capabilities,a hash of the received SUPL INIT message (ver) and a Location ID (lid)parameter indicating a serving cell (or serving WiFi AP) for UE 105 andpossibly serving cell (or serving WiFi AP) location measurements. The UE105 capabilities may include the supported positioning methods (e.g., UEAssisted A-GPS, UE Based A-GPS, OTDOA, and/or ECID) and associatedpositioning protocols (e.g., RRLP, RRC, TIA-801 or LPP/LPPe). The UE 105may include a request for Assistance Data in the SUPL POS INIT.

At stages F-I, the SLP 130 and UE 105 may exchange several successiveSUPL POS positioning messages. For example, at stage F, the SLP 130 maysend a SUPL POS message that includes an LPP Request Capabilitiesmessage.

At stage G, the UE 105 sends an SUPL POS message that includes an LPPProvide Capabilities message indicating the LPP positioning capabilitiesof UE 105.

At stage H, the SLP 130 may send assistance data to the UE 105 bysending a SUPL POS message that includes an LPP Provide Assistance Datamessage.

At stage I, the SLP 130 may request location information from the UE 105by sending another SUPL POS message that includes an LPP RequestLocation Information message. If desired, stages H and I may becombined, e.g., with the same SUPL POS message including an LPP ProvideAssistance Data message and an LPP Request Location Information message.

The UE 105 then sends an indication to the SLP 130 that the UE 105 isgoing to enter an idle state so that the UE 105 may obtain the requestedlocation information (e.g. based on UE 105 having just a single RFchain). The SUPL positioning session then ends. As indicated by boxes302 and 304, there are alternative ways in which the SUPL positioningsession may end. For example, as illustrated in box 302, at stage J, theUE 105 sends a message to the SLP 130 with an indication that the UE 105will enter idle mode, e.g., by sending a SUPL POS message with anembedded LPP Provide Location Information message. The LPP ProvideLocation Information, for example, may include a parameter, flag, causevalue, error cause value or LocationError value that indicates that theUE 105 will enter idle mode (also referred to herein as idle state). Theindication that the UE will enter the idle state may include an estimateof a time interval between a time of entering the idle state and a timeof re-entering a connected state.

At stage K, the SLP 130 sends a message to the UE 105 ending thelocation session, e.g., a SUPL END message. The UE 105 releases thesecure data connection to the SLP 130 and releases all resources relatedto this session.

As indicated by box 304, as an alternative to box 302, the UE 105 mayend the location session at the same time as indicating that the UE 105will enter idle mode. For example, at stage L, the UE 105 may send amessage to the SLP 130 ending the location session, e.g., a SUPL ENDmessage, that includes the indication that the UE 105 will enter idlemode, e.g., which may be encoded as a parameter, flag, cause value,error cause value or Status Code value in the message. The indicationthat the UE will enter the idle state may include an estimate of a timeinterval between a time of entering the idle state and a time ofre-entering a connected state. The SLP 130 then releases the secure dataconnection to the UE 105 and releases all resources related to thissession.

At stage M, the UE 105 enters an idle state in which the UE 105 is notconnected with the wireless network, e.g., there is no active signalingconnection to the network (e.g. such as a no signaling connection toE-UTRAN 112 or to NG-RAN 212).

At stage N, the UE 105 obtains the location measurements requested atstage I while in the idle state (e.g. using a single RF chain for UE105).

At stage O, the UE 105 reenters a connected state with the wirelessnetwork (e.g. with E-UTRAN 112 and EPC 120 or with NG-RAN 212 and 5GCN250) after the location measurements are obtained.

FIG. 4 is a signaling flow which continues the signaling flow in FIG. 3and illustrates the initiation of a second positioning session after theinitial positioning session illustrated in FIG. 3 is terminated byeither the SLP 130 or UE 105 (illustrated in FIG. 4 as stage A) and theUE 105 has reentered the connected state after obtaining the locationmeasurements (illustrated in FIG. 4 as stage B). At stage C in FIG. 4,the SLP 130 may wait a short time period, e.g., 30-120 seconds, duringwhich the UE 105 enters the idle state, obtains the locationmeasurements and re-enters a connected state (e.g. as at stages M, N andO in FIG. 3).

At stage D, the SLP 130 initiates a new SUPL positioning session withthe UE 105 by sending a SUPL INIT message to UE 105 (e.g. using SMS orUDP/IP). The new SUPL location session may be a copy of the initial SUPLlocation session, illustrated in FIG. 3, as the SUPL INIT message canprovide the same identification information as used in the initiallocation session. For example, the same Notification parameter may beincluded in the SUPL INIT message of stage C of FIG. 3 and the secondSUPL INIT message in stage D of FIG. 4.

In one embodiment, in addition to or instead of including the sameNotification parameter in the SUPL INIT message, the SLP 130 may includea session identification (ID) in the SUPL INIT message at stage D whichcan be associated with the session ID used for the initial SUPL locationsession. In SUPL, a session ID may comprise an SLP assigned session IDcombined with a separate SET (or UE) assigned session ID. An SLP sessionID can include an SLP address (e.g. an IP address or Fully QualifiedDomain Name (FQDN)) and an octet string (e.g. comprising four octets),which is referred to here as either a new or initial “SLP assigned octetstring” when applied to the new or initial SUPL location session,respectively. A SET session ID can include a SET ID (e.g. a MobileStation International Subscriber Directory Number (MSISDN) orInternational Mobile Subscriber Identity (IMSI)) and an integer (e.g.between zero and 65535), which is referred to here as either a new orinitial “SET assigned integer” when applied to the new or initial SUPLlocation session, respectively. For the new SUPL location session, theSLP 130 may include a new SLP assigned octet string (for a new sessionID) which includes, or is some mapping of (e.g. a mathematicaltransformation of), the initial SLP assigned octet string and/or theinitial SET assigned integer. For example, the SLP 130 could: (i) equatethe new SLP assigned octet string to the initial SLP assigned octetstring; (ii) include the initial SET assigned integer (when expressed inbinary) within the new SLP assigned octet string; or (iii) include part(e.g. low or high order bits) of the initial SLP assigned octet stringand part (e.g., low or high order bits) of the initial SET assignedinteger (when expressed in binary) in the new SLP assigned octet string.

At stage E, the UE 105 determines a correspondence of the new andinitial session IDs and/or of the identification information (e.g., theNotification parameters from the SUPL INIT message of stage C of FIG. 3and the second SUPL INIT message in stage D of FIG. 4). The UE 105 maythereby determine that the SUPL INIT message received at stage D of FIG.4 resumes the location session that was terminated in FIG. 3.

At stage F in FIG. 4, the UE 105 establishes or resumes a secure dataconnection with the SLP 130, e.g. using TCP and Transport Layer Security(TLS) protocols over IP. For example, the UE 105 may resume the securedata connection with the SLP 130 that was used for the first SUPLsession in FIG. 3. The secure data connection may then be used totransport further SUPL messages at stages G and I

At stage G, UE 105 sends a SUPL POS INIT message to the SLP 130. TheSUPL POS INIT message from the UE 105 includes, e.g., the locationinformation that was obtained while the UE 105 was in the idle state (atstage N in FIG. 3), e.g., as an LPP Provide Location Informationmessage.

At stage H, the SLP 130 determines (e.g. calculates) a position estimatefor the UE 105 based on the received location information.

At stage I, once the position determination is complete the SLP 130sends a SUPL END message to the UE 105 to end the location session. TheUE 105 releases the secure data connection to the SLP 130 and releaseall resources related to this session.

At stage J, the SLP 130 sends the position estimate back to the SUPLAgent 150, e.g. in an MLP Standard Location Immediate Answer (SLIA)message, and the SLP 130 releases all resources related to the session.

FIGS. 5 and 6 show a signaling flow illustrating a process ofdetermining a location for a UE 105 during which the UE 105 enters anidle state to obtain location measurements for a UE initiated SUPLsession. The signaling flow in FIGS. 5 and 6 may be applicable to the UE105 and SLP 130 in communication system 100 (e.g. when UE 105 has NB-IoTwireless access to eNB 110) or may be applicable to the UE 105 and SLP130 in communication system 200 (e.g. when UE 105 has NB-IoT wirelessaccess to an ng-eNB in NG-RAN 212 or has a future narrowband NR wirelessaccess to gNB 210-1). FIG. 5, for example, illustrates the initiationand termination of an initial positioning session when location isinitiated by UE 105. As illustrated, at stage A in FIG. 5, there is alocation request from an application (App) within the UE 105.

At stage B, the UE 105 establishes or resumes a secure data connectionwith the SLP 130, e.g. using TCP and Transport Layer Security (TLS)protocols over IP. The secure data connection may then be used totransport further SUPL messages at stage C and stages E-L.

At stage C, the UE initiates a SUPL positioning session by sending aSUPL START message to SLP 130. The SUPL START message contains asession-id, UE capabilities and Location ID (lid) parameter, and mayinclude an Application ID that identifies the App within the UE thatrequested the location information at stage A.

At stage D, the SLP 130 may verify that the UE 105 is authorized for theservice it requests based on identifiers received at stage B and/orstage C (e.g. an identification for UE 105).

At stage E, the SLP 130 determines a position method consistent with theSUPL START message (e.g. including position method(s) supported by theUE 105) and responds by sending a SUPL RESPONSE to the UE 105. The SUPLRESPONSE contains a session-id and the position method.

At stage E1, the UE 105 sends a SUPL POS INIT message to the SLP 130.The SUPL POS INIT message may contain, e.g., a session-id, UEcapabilities, and a Location ID (lid) parameter indicating a servingcell (or serving WiFi AP) for UE 105 and possibly serving cell (orserving WiFi AP) location measurements. The UE 105 capabilities mayinclude the supported positioning methods (e.g., UE Assisted A-GPS, UEBased A-GPS, OTDOA and/or ECID) and associated positioning protocols(e.g., RRLP, RRC, TIA-801 or LPP/LPPe). The UE 105 may include a requestfor Assistance Data in the SUPL POS INIT.

At stages F-I, the SLP 130 and UE 105 may exchange several successiveSUPL POS positioning messages. For example, at stage F, the SLP 130 maysend a SUPL POS message that includes an LPP Request Capabilitiesmessage.

At stage G, the UE 105 sends a SUPL POS message that includes an LPPProvide Capabilities message indicating the LPP positioning capabilitiesof UE 105.

At stage H, the SLP 130 may send assistance data to the UE 105 bysending a SUPL POS message that includes an LPP Provide Assistance Datamessage.

At stage I, the SLP 130 may request location information from the UE 105by sending another SUPL POS message that includes an LPP RequestLocation Information message. If desired, stages H and I may becombined, e.g., with the same SUPL POS message including an LPP ProvideAssistance Data message and an LPP Request Location Information message.

The UE 105 then sends an indication to the SLP 130 that the UE 105 isgoing to enter an idle state so that the UE 105 may obtain the requestedlocation information (e.g. based on UE 105 having just a single RFchain). The SUPL positioning session then ends. As indicated by boxes502 and 504, there are alternative ways in which the SUPL positioningsession may end. For example, as illustrated in box 502, at stage J, theUE 105 sends a message to the SLP 130 with an indication that the UE 105will enter idle mode, e.g., by sending a SUPL POS message with anembedded LPP Provide Location Information message. The LPP ProvideLocation Information, for example, may include a parameter, flag, causevalue, error cause value or LocationError value that indicates that theUE 105 will enter idle mode. The indication that the UE will enter theidle state may include an estimate of a time interval between a time ofentering the idle state and a time of re-entering a connected state.

At stage K, the SLP 130 sends a message to the UE 105 ending thelocation session, e.g., a SUPL END message. The UE 105 then releases thesecure data connection to the SLP 130 and releases all resources relatedto this session.

As indicated by box 504, as an alternative to box 502, the UE 105 mayend the location session at the same time as indicating that the UE 105will enter idle mode. For example, at stage L, the UE 105 may send amessage to the SLP 130 ending the location session, e.g., a SUPL ENDmessage, that includes the indication that the UE 105 will enter idlemode, e.g., which may be encoded as a parameter, flag, cause value,error cause value or Status Code value in the message. The indicationthat the UE will enter the idle state may include an estimate of a timeinterval between a time of entering the idle state and a time ofre-entering the connected state. The SLP 130 then releases the securedata connection to the UE 105 and releases all resources related to thissession.

At stage M, the UE 105 enters an idle state in which the UE 105 is notconnected with the wireless network, e.g., there is no active signalingconnection to the network (e.g. such as a no signaling connection toE-UTRAN 112 or to NG-RAN 212).

At stage N, the UE 105 obtains the requested location measurements whilein the idle state (e.g. using a single RF chain for UE 105).

At stage O, the UE 105 reenters a connected state with the wirelessnetwork (e.g. with E-UTRAN 112 and EPC 120 or with NG-RAN 212 and 5GCN250) after the location measurements are obtained.

FIG. 6 is a signaling flow which continues the signaling flow in FIG. 5and illustrates the initiation of a second SUPL positioning sessionafter the initial positioning session illustrated in FIG. 5 isterminated by either the SLP 130 or UE 105 (illustrated in FIG. 6 asstage A) and the UE 105 has reentered the connected state afterobtaining the location measurements (illustrated in FIG. 6 as stage B).

At stage C in FIG. 6, the UE 105 establishes or resumes a secure dataconnection with the SLP 130, e.g. using TCP and Transport Layer Security(TLS) protocols over IP. For example, the UE 105 may resume the securedata connection with the SLP 130 that was used for the first SUPLsession in FIG. 5. The secure data connection may then be used totransport further SUPL messages at stages D, F, G and I.

At stage D, the UE 105 initiates a new SUPL positioning session with theSLP 130 by sending a SUPL START message to SLP 130. The new locationsession is a copy of the initial location session, illustrated in FIG.5, as the SUPL START message can provide the same identificationinformation as used in the initial location session. For example, thesame Application ID parameter may be included in the SUPL START messageof stage C of FIG. 5 and the second SUPL START message in stage D ofFIG. 6.

In one embodiment, in addition to or instead of including the sameidentification information in the SUPL START message, the UE 105 mayinclude a session ID in the SUPL START message at stage D which can beassociated with the session ID used for the initial SUPL locationsession. For example, and using the same terminology as described forsession ID association for FIG. 4, the UE 105 may include a new SETassigned integer (for a new session ID) which includes all or part of,or is some mapping of all or part of (e.g. a mathematical transformationof), the initial SLP assigned octet string and/or the initial SETassigned integer. For example, the UE 105 could: (i) equate the new SETassigned integer to the initial SET assigned integer; (ii) include partof the initial SLP assigned octet string within the new SET assignedinteger (when expressed in binary); or (iii) include part (e.g. low orhigh order bits) of the initial SLP assigned octet string and part(e.g., low or high order bits) of the initial SET assigned integer (whenexpressed in binary) in the new SET assigned integer (when expressed inbinary).

At stage E in FIG. 6, the SLP 130 determines a correspondence of theidentification information, e.g., the Application ID parameters from theSUPL START message of stage C of FIG. 5 and the second SUPL STARTmessage in stage D of FIG. 6. The SLP 130 may thereby determine that theSUPL START message received at stage D of FIG. 6 resumes the locationsession that was terminated in FIG. 5.

At stage F in FIG. 6, the SLP 130 responds by sending a SUPL RESPONSE tothe UE 105. The SUPL RESPONSE may contain a session-id and a posmethodparameter.

At stage G, UE 105 sends a SUPL POS INIT message to the SLP 130. TheSUPL POS INIT message from the UE 105 includes, e.g., the locationinformation that was obtained while the UE 105 was in the idle state,e.g., as an LPP Provide Location Information message.

At stage H, the SLP 130 determines a position estimate of the UE 105based on the received location information.

At stage I, once the position determination is complete the SLP 130sends a SUPL END message to the UE 105 to provide the position estimateand to terminate the location session with the UE 105. The UE 105 thenreleases all resources related to the session.

In some embodiments, the signaling flow of FIG. 6 may follow thesignaling flow of FIG. 3, i.e., the initial location session may beinitiated by the SLP 130, as illustrated in FIG. 3, while the secondlocation session may be initiated by the UE 105, as illustrated in FIG.6. Similarly, the signaling flow of FIG. 4 may follow the signaling flowof FIG. 5, i.e., the initial location session may be initiated by the UE105, as illustrated in FIG. 5, while the second location session may beinitiated by the SLP 130, as illustrated in FIG. 4. In theseembodiments, the end (UE 105 or SLP 130) which initiates the secondlocation session may include a session ID for the second locationsession which can be associated with the session ID used for the initialSUPL location session, as described previously for FIGS. 4 and 6. Thismay enable the end which does not initiate the second location sessionto determine that the second location session is a continuation of theinitial location session.

FIG. 7 shows a process flow 700 illustrating a method of supportinglocation services for a user equipment (UE), e.g., when the UE is usingNB-IOT radio access or a (e.g. future) narrowband New Radio (NR) radioaccess to access (or connect to) a wireless network. In someembodiments, the process flow 700 may be performed by other UEs usingother types of radio access (e.g. LTE wideband access, NR access, WLANaccess or eMTC access)—e.g. if a UE has limited resources (e.g. limitedRF transceivers). The process flow 700 may be performed by the UE, suchas UE 105 in communication systems 100 and 200. The process flow 700 maystart at block 702, where the UE begins a first user plane locationsession (e.g. a SUPL session) with a location server, e.g., SLP 130 incommunication systems 100, 200. By way of example, the first user planelocation session may begin by the UE sending a message to the locationserver, such as a SUPL START message, e.g., as shown at stage C in FIG.5. The message sent by the UE, for example, may include anidentification parameter, such as an Application ID. In anotherimplementation, the first user plane location session may begin by theUE receiving a message from the location server, such as a SUPL INITmessage, e.g., as shown at stage C in FIG. 3. The message received bythe UE, for example, may include an identification parameter, such as aNotification parameter.

At block 704, a request for location measurements may be received fromthe location server, e.g., as illustrated at stage I in FIG. 3 and stageI in FIG. 5. For example, the request may be received in an LPP orLPP/LPPe Request Location Information message (e.g. which may betransported within a SUPL POS message). The location measurementsrequested may include measurements for one or more position methods suchas ECID, OTDOA, A-GNSS, WLAN, sensors etc. and/or may include a requestfor a location estimate for the UE.

At block 706, the UE sends an indication to the location server that theUE will enter an idle state in which the UE will not be connected with awireless network, and at block 708, the UE ends the first user planelocation session with the location server. The indication that the UEwill enter the idle state may be, e.g., a parameter, flag, cause value,error cause value, LocationError value or Status Code value in a messagesent to the location server. By way of example, in one implementation,the first user plane location session may end by the UE sending an endmessage (e.g. a SUPL END message) to the location server along with theindication that the UE will enter the idle state, e.g., as shown inboxes 304 and 504 in FIGS. 3 and 5. In another implementation, the UEmay send the indication that the UE will enter the idle state to thelocation server, e.g., as a parameter, flag, cause value, error causevalue, LocationError value or Status Code value in a message to thelocation server (e.g. an LPP Provide Location Information message), andthe first user plane location session may end by the location serversending an end message to the UE in response, e.g., as shown in boxes302 and 502 in FIGS. 3 and 5.

At block 710, the UE enters an idle state (e.g. by releasing a signalingconnection to the wireless network), e.g., as illustrated at stage M inFIG. 3 and stage M in FIG. 5. At block 712, the UE obtains the locationmeasurements while in the idle state, e.g., as illustrated at stage N inFIG. 3 and stage N in FIG. 5. At block 714, the UE re-enters a connectedstate with the wireless network (e.g. by requesting and obtaining a newsignaling connection to the wireless network), e.g., as illustrated atstage O in FIG. 3 and stage O in FIG. 5.

At block 716, the UE begins a second user plane location session (e.g. anew SUPL session) with the location server. The second user planelocation session may use an identification that is the same as theidentification used for the first user plane location session. Forexample, the identification may be (i) an Application Identification(ID) parameter where the first user plane location session is started bythe UE, (ii) a Notification parameter where the first user planelocation session is started by the location server, or (iii) a sessionID where the first user plane location session is started by either theUE or the location server. The second user plane location session maybegin by the UE sending a message (e.g. a SUPL START message) to thelocation server (e.g., as shown in stage D of FIG. 6), or by the UEreceiving a message (e.g. a SUPL INIT message) from the location server(e.g., as shown in stage D of FIG. 4).

At block 718, the UE sends the location measurements to the locationserver using the second user plane location session. For example, the UEmay send the location measurements to the location server in an LPP orLPP/LPPe Provide Location Information message (e.g. which may betransported in a SUPL POS INIT message), e.g., as shown at stage G inFIG. 4 and stage G in FIG. 6.

By way of example, in one implementation, the first user plane locationsession with the location server may begin (at block 702) by the UEsending a first message to the location server, e.g., as shown at stageC in FIG. 5, or the UE receiving a second message from the locationserver, e.g. as shown at stage C in FIG. 3, and the second user planelocation session with the location server may begin (at block 716) bythe UE sending a third message to the location server, e.g., as shown atstage D in FIG. 6, or receiving a fourth message from the locationserver, e.g., as shown at stage D in FIG. 4. Here, the first message andthe third message may comprise a first message type and the secondmessage and the fourth message may comprise a second message type. Forexample, the first message type may be a Secure User Plane Location(SUPL) START message type and the second message type may be a SUPL INITmessage type. For example, in one implementation, the UE may receive thesecond message, where the second message comprises a first notificationparameter; receive the fourth message, where the fourth messagecomprises a second notification parameter, verify that the firstnotification parameter is the same as the second notification parameter,and send the location measurements to the location server using thesecond user plane location session, based on the verification. Inanother implementation, the UE may send the first message, where thefirst message comprises an application identification (ID), and send thethird message, where the third message comprises the (same) applicationID. In a further implementation, the UE may receive the fourth message,where the fourth message comprises a new session identification (ID),verify the new session ID is associated with (e.g. includes part of oris a mapping of part of) an initial session ID for the first user planelocation session, and send the location measurements to the locationserver using the second user plane location session, based on theverification. In another implementation, the UE may send the thirdmessage, where the third message comprises a new session identification(ID), and where the new session ID is associated with (e.g. includespart of or is a mapping of part of) an initial session ID for the firstuser plane location session.

In one implementation, the first user plane location session with thelocation server may end (at block 708) by the UE sending a fifth messageto the location server, e.g., as shown at stage L in FIG. 3 and stage Lin FIG. 5, or the UE receiving a sixth message from the location server,e.g., as shown at stage K in FIG. 3 and stage K in FIG. 5. For example,the fifth message and the sixth message may each be a Secure User PlaneLocation (SUPL) END message. Additionally, the indication that the UEwill enter the idle state (at block 706) may be a parameter, flag, causevalue, error cause value, LocationError value or Status Code value in aseventh message sent to the location server. The indication that the UEwill enter the idle state may include an estimate of a time intervalbetween a time of entering the idle state and a time of re-entering theconnected state. In some implementations, the seventh message maycomprise the fifth message or a positioning protocol message. Thepositioning protocol message for example, may be a Long Term Evolution(LTE) Positioning Protocol (LPP) Provide Location Information (PLI)message, where the LPP PLI message is sent to the location server in aSecure User Plane Location (SUPL) POS message, e.g. as shown for stage Jof FIG. 3 and stage J of FIG. 5.

FIG. 8 shows a process flow 800 illustrating a method of supportinglocation services for a user equipment (UE), e.g., when the UE is usingNB-IOT radio access or a (e.g. future) narrowband New Radio (NR) radioaccess to access (or connect to) a wireless network. In someembodiments, the process flow 800 may support location services for UEsusing other types of radio access (e.g. LTE wideband access, NR access,WLAN access or eMTC access)—e.g. if a UE has limited resources (e.g.limited RF transceivers). The process flow 800 may be performed by thelocation server, such as SLP 130 in communication systems 100 and 200.The process flow 800 may start at block 802, where the location serverbegins a first user plane location session (e.g. a SUPL session) withthe UE, e.g., UE 105 in communication systems 100, 200. By way ofexample, the first user plane location session may be started by thelocation server receiving a message from the UE, such as a SUPL STARTmessage, e.g., as shown at stage C in FIG. 5. The message received fromthe UE, for example, may include an identification parameter, such as anApplication ID. In another implementation, the first user plane locationsession may begin by the location server sending a message to the UE,such as a SUPL INIT message, e.g., as shown at stage C in FIG. 3. Themessage sent by the location server, for example, may include anidentification parameter, such as a Notification parameter.

At block 804, the location server sends a request for locationmeasurements to the UE, e.g., as illustrated at stage I in FIG. 3 andstage I in FIG. 5. For example, the location server may send an LPP orLPP/LPPe Request Location Information message to the UE (e.g.transported in a SUPL POS message). The location measurements requestedmay include measurements for one or more position methods such as ECID,OTDOA, A-GNSS, WLAN, sensors etc. and/or may include a request for alocation estimate for the UE.

At block 806, the location server receives an indication from the UEthat the UE will enter an idle state in which the UE will not beconnected with a wireless network and during which the UE will obtainthe location measurements. At block 808, the location server ends thefirst user plane location session with the UE. The indication that theUE will enter the idle state may be, e.g., a flag or an error messagereceived by the location server. By way of example, in oneimplementation, the first user plane location session may end by thelocation server receiving an end message (e.g. a SUPL END message) fromthe UE along with the indication that the UE will enter the idle state,e.g., as shown in boxes 304 and 504 in FIGS. 3 and 5. In anotherimplementation, the location server may receive the indication that theUE will enter the idle state, e.g., as a parameter, flag, cause value,error cause value, LocationError value or Status Code value in a messagesent to the location server (e.g. an LPP Provide Location Informationmessage), and the first user plane location session may end by thelocation server sending an end message to the UE (e.g. a SUPL ENDmessage) in response, e.g., as shown in boxes 302 and 502 in FIGS. 3 and5.

At block 810, the location server begins a second user plane locationsession (e.g. a new SUPL session) with the UE. The second user planelocation session may use an identification that is the same as theidentification used for the first user plane location session. Forexample, the identification may be (i) an Application Identification(ID) parameter where the first user plane location session is started bythe UE, (ii) a Notification parameter where the first user planelocation session is started by the location server, or (iii) a sessionID where the first user plane location session is started by either theUE or the location server. The second user plane location session maybegin by the location server receiving a message (e.g. a SUPL STARTmessage) from the UE (e.g., as shown in stage D of FIG. 6), or by thelocation server sending a message (e.g. a SUPL INIT message) to the UE(e.g., as shown in stage D of FIG. 4).

At block 812, the location measurements are received from the UE usingthe second user plane location session. For example, the locationmeasurements may be received in an LPP or LPP/LPPe Provide LocationInformation message sent to the location server by the UE (e.g.transported in a SUPL POS INIT message), e.g., as shown at stage G inFIG. 4 and stage G in FIG. 6.

At block 814, the location of the UE is determined using the locationmeasurements, e.g., as shown at stage H in FIG. 4 and stage H in FIG. 6.For example, the location server may calculate a location for the UEusing almanac data (e.g. BSA data) configured in the location server inthe case of location measurements for the ECID, OTDOA or WLAN positionmethods and/or using GNSS ephemeris and timing data for locationmeasurements for the GNSS or A-GNSS position method.

In one implementation, the location server may send the location of theUE to an external client, e.g., as illustrated at stage J of FIG. 4. Inone implementation, the location server may send the location of the UEto the UE, e.g. as illustrated at stage I of FIG. 6.

By way of example, in some implementations, the first user planelocation session with the UE may begin (at block 802) by the locationserver sending a first message to the UE, e.g., as shown at stage C inFIG. 3, or receiving a second message from the UE, e.g., as shown atstage C in FIG. 5, and the second user plane location session with theUE may begin (at block 810) by the location server sending a thirdmessage to the UE, e.g., as shown at stage D in FIG. 4, or receiving afourth message from the UE, e.g., as shown at stage D in FIG. 6. Here,the first message and the third message may comprise a first messagetype and the second message and the fourth message may comprise a secondmessage type. For example, the first message type may be a Secure UserPlane Location (SUPL) INIT message type and the second message type maybe a SUPL START message type. For example, in one implementation, thelocation server may receive the second message, where the second messagecomprises a first application identification (ID), receive the fourthmessage, where the fourth message comprises a second application ID,verify the first application ID is the same as the second applicationID, and determine the location of the UE using the locationmeasurements, based on the verification. In another implementation, thelocation server may send the first message, where the first messagecomprises a notification, and send the third message, where the thirdmessage comprises the (same) notification. In a further implementation,the location server may receive the fourth message, where the fourthmessage comprises a new session identification (ID), verify the newsession ID is associated with (e.g. includes part of or is a mapping ofpart of) an initial session ID for the first user plane locationsession, and determine the location of the UE using the locationmeasurements, based on the verification. In another implementation, thelocation server may send the third message, where the third messagecomprises a new session identification (ID), and where the new sessionID is associated with (e.g. includes part of or is a mapping of part of)an initial session ID for the first user plane location session.

In one implementation, the first user plane location session with the UEmay end (at block 808) by the location server sending a fifth message tothe UE, e.g., as shown at stage K in FIG. 3 and stage K in FIG. 5, orreceiving a sixth message from the UE, e.g., as shown at stage L in FIG.3 and stage L in FIG. 5. For example, the fifth message and the sixthmessage may each be a Secure User Plane Location (SUPL) END message.Additionally, the indication that the UE will enter the idle state maycomprise a parameter, flag, cause value, error cause value,LocationError value or Status Code value in a seventh message receivedfrom the UE. In some implementations, the indication that the UE willenter the idle state may include an estimate of a time interval betweena time of entering the idle state at the UE and a time of re-entering aconnected state at the UE. In some implementations, the seventh messagecomprises the sixth message or a positioning protocol message. Thepositioning protocol message may comprise a Long Term Evolution (LTE)Positioning Protocol (LPP) Provide Location Information (PLI) message,where the LPP PLI message is received by the location server in a SecureUser Plane Location (SUPL) POS message.

FIG. 9 is a diagram illustrating an example of a hardware implementationof a user equipment (UE) 900, which may be the UE 105 shown in FIGS.1-6. The UE 900 may include a WWAN transceiver 902 to wirelesslycommunicate with, e.g., cellular transceivers such as an eNB 110 (shownin FIG. 1) or a gNB 210 (shown in FIG. 2). The UE 900 may also include aWLAN transceiver 904 to wirelessly communicate with local transceivers(e.g. WiFi APs or BT beacons). The UE 900 may include one or moreantennas 906 that may be used with the WWAN transceiver 902 and WLANtransceiver 904. The UE 900 may further include an SPS receiver 908 forreceiving and measuring signals from SPS SVs 160 (shown in FIGS. 1 and2), received via antenna(s) 906. The UE 900 may include one or moresensors 910, such as cameras, accelerometers, gyroscopes, electroniccompass, magnetometer, barometer, etc. The UE 900 may further include auser interface 912 that may include e.g., a display, a keypad or otherinput device, such as virtual keypad on the display, through which auser may interface with the UE 900.

The UE 900 further includes one or more processors 914 and memory 920,which may be coupled together with a bus 916. The one or more processors914 and other components of the UE 900 may similarly be coupled togetherwith bus 916, a separate bus, or may be directly connected together orcoupled using a combination of the foregoing. The memory 920 may containexecutable code or software (or firmware) instructions that whenexecuted by the one or more processors 914 cause the one or moreprocessors 914 to operate as a special purpose computer programmed toperform the techniques disclosed herein. As illustrated in FIG. 9, thememory 920 may include one or more components or modules that may beimplemented by the one or more processors 914 to perform themethodologies described herein. While the components or modules areillustrated as software in memory 920 that is executable by the one ormore processors 914, it should be understood that the components ormodules may be dedicated hardware either in the one or more processors914 or off the processors.

The memory 920 may include a begin position session unit 922 that whenimplemented by the one or more processors 914 configures the one or moreprocessors 914 to engage in a user plane positioning session with alocation server (e.g. SLP 130), e.g., including configuring the one ormore processors 914 to send and/or receive messages (e.g. SUPL messages)via WWAN transceiver 902 and/or WLAN transceiver 904 to initiate thepositioning session. A location measurement request receive unit 924,when implemented by the one or more processors 914, configures the oneor more processors 914 to receive messages with a request for locationmeasurements via WWAN transceiver 902 and/or WLAN transceiver 904. Anidle state indicator unit 926, when implemented by the one or moreprocessors 914, configures the one or more processors 914 to send amessage (e.g. a SUPL message or a positioning protocol message) via WWANtransceiver 902 and/or WLAN transceiver 904 with an indication that theUE 900 will enter an idle state in which the UE 900 will not beconnected with a wireless network. For example, the indication may be aparameter, flag, cause value, error cause value, LocationError value orStatus Code value in the message. When implemented by the one or moreprocessors 914, the idle state indicator unit 926 may cause the one ormore processors 914 to provide an estimate of a time interval between atime of entering the idle state and a time of re-entering a connectedstate that may be sent in a positioning session.

An end position session unit 928, when implemented by the one or moreprocessors 914, configures the one or more processors 914 to end theuser plane positioning session with the location server, e.g., includingconfiguring the one or more processors 914 to send and/or receivemessages (e.g. SUPL messages) via WWAN transceiver 902 and/or WLANtransceiver 904 to end the positioning session.

The memory may further include an idle unit 930 that when implemented bythe one or more processors 914 configures the one or more processors 914to enter the idle state in which the UE 900 is not connected with awireless network. When implemented by the one or more processors 914,the idle unit 930 may further cause the one or more processors 914 tore-enter a connected state with the wireless network after locationmeasurements are obtained.

The memory 920 may further include a location measurement unit 932 thatwhen implemented by the one or more processors 914 configures the one ormore processors 914 to obtain location measurements, e.g., using one ormore of the WWAN transceiver 902, WLAN transceiver 904 and SPS Receiver908. For example, the location measurements may include at least one ofa cell ID, RSSI, RSRP, RSRQ, RSTD, RTT, pseudorange, code phase orcarrier phase measurement. When implemented by the one or moreprocessors 914, the location measurement unit 932 may cause the locationmeasurements to be obtained after the UE 900 is in an idle state. Alocation measurement report unit 934, when implemented by the one ormore processors 914, configures the one or more processors 914 to sendthe location measurements obtained via the location measurement unit 932to the location server, e.g., via WWAN transceiver 902 and/or WLANtransceiver 904, after the UE 900 has reentered a connected state.

The methodologies described herein may be implemented by various meansdepending upon the application. For example, these methodologies may beimplemented in hardware, firmware, software, or any combination thereof.For a hardware implementation, the one or more processors 914 may beimplemented within one or more application specific integrated circuits(ASICs), digital signal processors (DSPs), digital signal processingdevices (DSPDs), programmable logic devices (PLDs), field programmablegate arrays (FPGAs), processors, controllers, micro-controllers,microprocessors, electronic devices, other electronic units designed toperform the functions described herein, or a combination thereof.

For an implementation of UE 900 involving firmware and/or software, themethodologies may be implemented with modules (e.g., procedures,functions, and so on) that perform the separate functions describedherein. Any machine-readable medium tangibly embodying instructions maybe used in implementing the methodologies described herein. For example,software codes may be stored in a memory (e.g. memory 920) and executedby one or more processors 914, causing the one or more processors 914 tooperate as a special purpose computer programmed to perform thetechniques disclosed herein. Memory may be implemented within the one orprocessors 914 or external to the one or more processors 914. As usedherein the term “memory” refers to any type of long term, short term,volatile, nonvolatile, or other memory and is not to be limited to anyparticular type of memory or number of memories, or type of media uponwhich memory is stored.

If implemented in firmware and/or software, the functions performed byUE 900 may be stored as one or more instructions or code on anon-transitory computer-readable storage medium such as memory 920.Examples of storage media include computer-readable media encoded with adata structure and computer-readable media encoded with a computerprogram. Computer-readable media includes physical computer storagemedia. A storage medium may be any available medium that can be accessedby a computer. By way of example, and not limitation, suchcomputer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or otheroptical disk storage, magnetic disk storage, semiconductor storage, orother storage devices, or any other medium that can be used to storedesired program code in the form of instructions or data structures andthat can be accessed by a computer; disk and disc, as used herein,includes compact disc (CD), laser disc, optical disc, digital versatiledisc (DVD), floppy disk and Blu-ray disc where disks usually reproducedata magnetically, while discs reproduce data optically with lasers.Combinations of the above should also be included within the scope ofcomputer-readable media.

In addition to storage on computer-readable storage medium, instructionsand/or data for UE 900 may be provided as signals on transmission mediaincluded in a communication apparatus. For example, a communicationapparatus comprising part or all of UE 900 may include a transceiverhaving signals indicative of instructions and data. The instructions anddata are stored on non-transitory computer readable media, e.g., memory920, and are configured to cause the one or more processors 914 tooperate as a special purpose computer programmed to perform thetechniques disclosed herein. That is, the communication apparatusincludes transmission media with signals indicative of information toperform disclosed functions. At a first time, the transmission mediaincluded in the communication apparatus may include a first portion ofthe information to perform the disclosed functions, while at a secondtime the transmission media included in the communication apparatus mayinclude a second portion of the information to perform the disclosedfunctions.

Thus, a UE 900 may include a means for beginning a first user planelocation session with a location server, which may be, e.g., at leastone wireless transceiver such as the WWAN transceiver 902 and/or WLANtransceiver 904 and one or more processors 914 with dedicated hardwareor implementing executable code or software instructions in memory 920such as the begin position session unit 922. A means for receiving arequest for location measurements from the location server may be, e.g.,at least one wireless transceiver such as the WWAN transceiver 902and/or WLAN transceiver 904 and one or more processors 914 withdedicated hardware or implementing executable code or softwareinstructions in memory 920 such as the location measurement requestreceive unit 924. A means for sending an indication to the locationserver that the UE 900 will enter an idle state in which the UE 900 willnot be connected with a wireless network may be, e.g., at least onewireless transceiver such as the WWAN transceiver 902 and/or WLANtransceiver 904 and one or more processors 914 with dedicated hardwareor implementing executable code or software instructions in memory 920such as the idle state indicator unit 926. A means for ending the firstuser plane location session with the location server may be, e.g., atleast one wireless transceiver such as the WWAN transceiver 902 and/orWLAN transceiver 904 and one or more processors 914 with dedicatedhardware or implementing executable code or software instructions inmemory 920 such as the end position session unit 928. A means forentering the idle state may be, e.g., one or more processors 914 withdedicated hardware or implementing executable code or softwareinstructions in memory 920 such as the idle unit 930. A means forobtaining the location measurements while in the idle state may be,e.g., at least one wireless transceiver such as the WWAN transceiver 902and/or WLAN transceiver 904 and/or SPS receiver 908 and one or moreprocessors 914 with dedicated hardware or implementing executable codeor software instructions in memory 920 such as the location measurementunit 932. A means for re-entering a connected state with the wirelessnetwork may be, e.g., at least one wireless transceiver such as the WWANtransceiver 902 and/or WLAN transceiver 904 and one or more processors914 with dedicated hardware or implementing executable code or softwareinstructions in memory 920 such as the idle unit 930. A means forbeginning a second user plane location session with the location servermay be, e.g., at least one wireless transceiver such as the WWANtransceiver 902 and/or WLAN transceiver 904 and one or more processors914 with dedicated hardware or implementing executable code or softwareinstructions in memory 920 such as the begin position session unit 922.A means for sending the location measurements to the location serverusing the second user plane location session may be, e.g., at least onewireless transceiver such as the WWAN transceiver 902 and/or WLANtransceiver 904 and one or more processors 914 with dedicated hardwareor implementing executable code or software instructions in memory 920such as the location measurement report unit 934.

FIG. 10 is a diagram illustrating an example of a hardwareimplementation of a location server 1000, such as SLP 130, which may be,e.g., an H-SLP, E-SLP, or D-SLP, illustrated in FIGS. 1-6. The locationserver 1000 includes, e.g., hardware components such as an externalinterface 1002, which may be a wired or wireless interface capable ofconnecting to UE 105 directly or through one or more intermediarynetworks (e.g. E-UTRAN 112, NG-RAN 212, EPC 120 and/or 5GCN 250) and/orone or more network entities (e.g. eNB 110-1, SGW 126 and PDG 128 inFIG. 1 or gNB 210-1 and UPF 257 in FIG. 2). The location server 1000 mayinclude a clock 1008 that may be used to determine a time period after apositioning session with the UE 105 has ended before a new positionsession with the UE 105 is initiated by the location server 1000. Thelocation server 1000 includes one or more processors 1004 and memory1010, which may be coupled together with a bus 1006. The memory 1010 maycontain executable code or software (or firmware) instructions that whenexecuted by the one or more processors 1004 cause the one or moreprocessors 1004 to operate as a special purpose computer programmed toperform the techniques disclosed herein.

As illustrated in FIG. 10, the memory 1010 may include one or morecomponents or modules that may be implemented by the one or moreprocessors 1004 to perform the methodologies as described herein. Whilethe components or modules are illustrated as software in memory 1010that is executable by the one or more processors 1004, it should beunderstood that the components or modules may be dedicated hardwareeither in the one or more processors 1004 or off the processors. Itshould be understood that, since the location server 1000 can correspondto a number of different network entities, not all the functions andcomponents for the location server 1000 described herein may be presentfor any particular example of the location server 1000.

For example, the memory 1010 may include a begin position session unit1012 that when implemented by the one or more processors 1004 configuresthe one or more processors 1004 to engage in a user plane (e.g. SUPL)positioning session with a UE (e.g. UE 105) on behalf of an externalclient (e.g. external client 150), e.g., including configuring the oneor more processors 1004 to send and/or receive messages (e.g. SUPLmessages) via external interface 1002 to initiate the positioningsession. A location measurement request unit 1014, when implemented bythe one or more processors 1004, configures the one or more processors1004 to send messages with a request for location measurements via theexternal interface 1002. An idle state receive unit 1016, whenimplemented by the one or more processors 1004, configures the one ormore processors 1004 to receive messages with an indication that the UEwill enter an idle state in which the UE will not be connected with awireless network and during which the UE will obtain the locationmeasurements.

The memory 1010 may further include a wait unit 1018 that whenimplemented by the one or more processors 1004 configures the one ormore processors 1004 to wait a specific time period, determined by theclock 1008, after a positioning session with the UE has ended and beforea new positioning session with the UE is begun, e.g., either initiatedby the location server 1000 or by the UE. The time period to wait may bea configured parameter and may be, e.g., 30-120 seconds. In someimplementations, the time period may be based on an estimate provided bythe UE of a time interval between a time of entering the idle state atthe UE and a time of re-entering a connected state at the UE. A locationmeasurement receive unit 1020, when implemented by the one or moreprocessors 1004, configures the one or more processors 1004 to receivelocation measurements from the UE via the external interface 1002.

The memory 1010 may further include a location determination unit 1022that when implemented by the one or more processors 1004 configures theone or more processors 1004 to determine a location of the UE using thelocation measurements received from the UE. A location report unit 1024,when implemented by the one or more processors 1004, configures the oneor more processors 1004 to send messages to the UE and/or externalclient with the location of the UE that is determined using the locationmeasurements.

The methodologies described herein may be implemented by various meansdepending upon the application. For example, these methodologies may beimplemented in location server 1000 using hardware, firmware, software,or any combination thereof. For a hardware implementation, the one ormore processors 1004 may be implemented within one or more applicationspecific integrated circuits (ASICs), digital signal processors (DSPs),digital signal processing devices (DSPDs), programmable logic devices(PLDs), field programmable gate arrays (FPGAs), processors, controllers,micro-controllers, microprocessors, electronic devices, other electronicunits designed to perform the functions described herein, or acombination thereof.

For an implementation of location server 1000 involving firmware and/orsoftware, the methodologies may be implemented with modules (e.g.,procedures, functions, and so on) that perform the separate functionsdescribed herein. Any machine-readable medium tangibly embodyinginstructions may be used in implementing the methodologies describedherein. For example, software codes may be stored in a memory andexecuted by one or more processor units, causing the processor units tooperate as a special purpose computer programmed to perform thetechniques disclosed herein. Memory may be implemented within the one ormore processors 1004 or external to the one or processors 1004 (e.g. asmemory 1010). As used herein the term “memory” refers to any type oflong term, short term, volatile, nonvolatile, or other memory and is notto be limited to any particular type of memory or number of memories, ortype of media upon which memory is stored.

If implemented in firmware and/or software in location server 1000, thefunctions described herein may be stored as one or more instructions orcode on a non-transitory computer-readable storage medium. Examplesinclude computer-readable media encoded with a data structure andcomputer-readable media encoded with a computer program.Computer-readable media includes physical computer storage media. Astorage medium may be any available medium that can be accessed by acomputer. By way of example, and not limitation, such computer-readablemedia can comprise RAM, ROM, EEPROM, CD-ROM or other optical diskstorage, magnetic disk storage, semiconductor storage, or other storagedevices, or any other medium that can be used to store desired programcode in the form of instructions or data structures and that can beaccessed by a computer; disk and disc, as used herein, includes compactdisc (CD), laser disc, optical disc, digital versatile disc (DVD),floppy disk and Blu-ray disc where disks usually reproduce datamagnetically, while discs reproduce data optically with lasers.Combinations of the above should also be included within the scope ofcomputer-readable media.

In addition to storage on computer-readable storage medium, instructionsand/or data for location server 1000 may be provided as signals ontransmission media included in a communication apparatus that maycomprise part or all of location server 1000. For example, acommunication apparatus may include a transceiver having signalsindicative of instructions and data. The instructions and data arestored on non-transitory computer readable media, e.g., memory 1010, andare configured to cause the one or more processors 1004 to operate as aspecial purpose computer programmed to perform the techniques disclosedherein. That is, the communication apparatus includes transmission mediawith signals indicative of information to perform disclosed functions.At a first time, the transmission media included in the communicationapparatus may include a first portion of the information to perform thedisclosed functions, while at a second time the transmission mediaincluded in the communication apparatus may include a second portion ofthe information to perform the disclosed functions.

Thus, a location server 1000 may include a means for beginning a firstuser plane location session with a UE, which may be, e.g., the externalinterface 1002 and one or more processors 1004 with dedicated hardwareor implementing executable code or software instructions in memory 1010such as the begin position session unit 1012. A means for sending arequest for location measurements to the UE may be, e.g., the externalinterface 1002 and one or more processors 1004 with dedicated hardwareor implementing executable code or software instructions in memory 1010such as the location measurement request unit 1014. A means forreceiving an indication from the UE that the UE will enter an idle statein which the UE will not be connected with a wireless network and duringwhich the UE will obtain the location measurements may be, e.g., theexternal interface 1002 and one or more processors 1004 with dedicatedhardware or implementing executable code or software instructions inmemory 1010 such as the idle state receive unit 1016. A means for endingthe first user plane location session with the UE may be, e.g., theexternal interface 1002 and one or more processors 1004 with dedicatedhardware or implementing executable code or software instructions inmemory 1010 such as the wait unit 1018. A means for beginning a seconduser plane location session with the UE may be, e.g., the externalinterface 1002 and one or more processors 1004 with dedicated hardwareor implementing executable code or software instructions in memory 1010such as the begin position session unit 1012. A means for receiving thelocation measurements from the UE using the second user plane locationsession may be, e.g., the external interface 1002 and one or moreprocessors 1004 with dedicated hardware or implementing executable codeor software instructions in memory 1010 such as the location measurementreceive unit 1020. A means for determining the location of the UE usingthe location measurements may be, e.g., the external interface 1002 andone or more processors 1004 with dedicated hardware or implementingexecutable code or software instructions in memory 1010 such as thelocation determination unit 1022.

Reference throughout this specification to “one example”, “an example”,“certain examples”, or “exemplary implementation” means that aparticular feature, structure, or characteristic described in connectionwith the feature and/or example may be included in at least one featureand/or example of claimed subject matter. Thus, the appearances of thephrase “in one example”, “an example”, “in certain examples” or “incertain implementations” or other like phrases in various placesthroughout this specification are not necessarily all referring to thesame feature, example, and/or limitation. Furthermore, the particularfeatures, structures, or characteristics may be combined in one or moreexamples and/or features.

Some portions of the detailed description included herein are presentedin terms of algorithms or symbolic representations of operations onbinary digital signals stored within a memory of a specific apparatus orspecial purpose computing device or platform. In the context of thisparticular specification, the term specific apparatus or the likeincludes a general purpose computer once it is programmed to performparticular operations pursuant to instructions from program software.Algorithmic descriptions or symbolic representations are examples oftechniques used by those of ordinary skill in the signal processing orrelated arts to convey the substance of their work to others skilled inthe art. An algorithm is here, and generally, is considered to be aself-consistent sequence of operations or similar signal processingleading to a desired result. In this context, operations or processinginvolve physical manipulation of physical quantities. Typically,although not necessarily, such quantities may take the form ofelectrical or magnetic signals capable of being stored, transferred,combined, compared or otherwise manipulated. It has proven convenient attimes, principally for reasons of common usage, to refer to such signalsas bits, data, values, elements, symbols, characters, terms, numbers,numerals, or the like. It should be understood, however, that all ofthese or similar terms are to be associated with appropriate physicalquantities and are merely convenient labels. Unless specifically statedotherwise, as apparent from the discussion herein, it is appreciatedthat throughout this specification discussions utilizing terms such as“processing,” “computing,” “calculating,” “determining” or the likerefer to actions or processes of a specific apparatus, such as a specialpurpose computer, special purpose computing apparatus or a similarspecial purpose electronic computing device. In the context of thisspecification, therefore, a special purpose computer or a similarspecial purpose electronic computing device is capable of manipulatingor transforming signals, typically represented as physical electronic ormagnetic quantities within memories, registers, or other informationstorage devices, transmission devices, or display devices of the specialpurpose computer or similar special purpose electronic computing device.

In the preceding detailed description, numerous specific details havebeen set forth to provide a thorough understanding of claimed subjectmatter. However, it will be understood by those skilled in the art thatclaimed subject matter may be practiced without these specific details.In other instances, methods and apparatuses that would be known by oneof ordinary skill have not been described in detail so as not to obscureclaimed subject matter.

The terms, “and”, “or”, and “and/or” as used herein may include avariety of meanings that also are expected to depend at least in partupon the context in which such terms are used. Typically, “or” if usedto associate a list, such as A, B or C, is intended to mean A, B, and C,here used in the inclusive sense, as well as A, B or C, here used in theexclusive sense. In addition, the term “one or more” as used herein maybe used to describe any feature, structure, or characteristic in thesingular or may be used to describe a plurality or some othercombination of features, structures or characteristics. Though, itshould be noted that this is merely an illustrative example and claimedsubject matter is not limited to this example.

While there has been illustrated and described what are presentlyconsidered to be example features, it will be understood by thoseskilled in the art that various other modifications may be made, andequivalents may be substituted, without departing from claimed subjectmatter. Additionally, many modifications may be made to adapt aparticular situation to the teachings of claimed subject matter withoutdeparting from the central concept described herein.

One implementation (1) may be a method for supporting location servicesfor a user equipment (UE) performed by a location server, comprising:beginning a first user plane location session with the UE; sending arequest for location measurements to the UE; receiving an indicationfrom the UE that the UE will enter an idle state in which the UE willnot be connected with a wireless network and during which the UE willobtain the location measurements; ending the first user plane locationsession with the UE; beginning a second user plane location session withthe UE; receiving the location measurements from the UE using the seconduser plane location session; and determining the location of the UEusing the location measurements.

There may be some implementations (2) of the above described method (1),wherein beginning the first user plane location session with the UEcomprises sending a first message to the UE or receiving a secondmessage from the UE, wherein beginning the second user plane locationsession with the UE comprises sending a third message to the UE orreceiving a fourth message from the UE, wherein the first message andthe third message comprise a first message type and the second messageand the fourth message comprise a second message type.

There may be some implementations (3) of the above described method (2),wherein the first message type is a Secure User Plane Location (SUPL)INIT message type and the second message type is a SUPL START messagetype.

There may be some implementations (4) of the above described method (1),wherein ending the first user plane location session with the UEcomprises sending a fifth message to the UE or receiving a sixth messagefrom the UE.

There may be some implementations (5) of the above described method (4),wherein the fifth message and the sixth message are each a Secure UserPlane Location (SUPL) END message.

There may be some implementations (6) of the above described method (4),wherein the indication that the UE will enter the idle state comprises aparameter, flag, cause value, error cause value, LocationError value orStatus Code value in a seventh message received from the UE.

There may be some implementations (7) of the above described method (6),wherein the indication that the UE will enter the idle state furthercomprises an estimate of a time interval between a time of entering theidle state at the UE and a time of re-entering a connected state at theUE.

There may be some implementations (8) of the above described method (6),wherein the seventh message comprises the sixth message or a positioningprotocol message.

There may be some implementations (9) of the above described method (8),wherein the positioning protocol message comprises a Long Term Evolution(LTE) Positioning Protocol (LPP) Provide Location Information (PLI)message, wherein the LPP PLI message is received by the location serverin a Secure User Plane Location (SUPL) POS message.

There may be some implementations (10) of the above described method(2), further comprising: receiving the second message, wherein thesecond message comprises a first application identification (ID);receiving the fourth message, wherein the fourth message comprises asecond application ID; verifying the first application ID is the same asthe second application ID; and determining the location of the UE usingthe location measurements, based on the verification.

There may be some implementations (11) of the above described method(2), further comprising: sending the first message, wherein the firstmessage comprises a notification; and sending the third message, whereinthe third message comprises the notification.

There may be some implementations (12) of the above described method(2), further comprising: receiving the fourth message, wherein thefourth message comprises a new session identification (ID); verifyingthe new session ID is associated with an initial session ID for thefirst user plane location session; and determining the location of theUE using the location measurements, based on the verification.

There may be some implementations (13) of the above described method(2), further comprising: sending the third message, wherein the thirdmessage comprises a new session identification (ID), wherein the newsession ID is associated with an initial session ID for the first userplane location session.

There may be some implementations (14) of the above described method(1), further comprising sending the location of the UE to an externalclient.

There may be some implementations (15) of the above described method(1), further comprising sending the location of the UE to the UE.

There may be some implementations (16) of the above described method(1), wherein the user equipment (UE) is connected to the wirelessnetwork using Narrowband Internet of Things (NB-IoT) radio access or anarrowband New Radio (NR) radio access.

One implementation (17) may be a location server for supporting locationservices for a user equipment (UE), comprising: an external interfaceconfigured to communicate with a wireless network; and at least oneprocessor coupled to the external interface and configured to begin viathe external interface a first user plane location session with the UE,send via the external interface a request for location measurements tothe UE, receive via the external interface an indication from the UEthat the UE will enter an idle state in which the UE will not beconnected with the wireless network and during which the UE will obtainthe location measurements, end via the external interface the first userplane location session with the UE, begin via the external interface asecond user plane location session with the UE, receive via the externalinterface the location measurements from the UE using the second userplane location session, and determine the location of the UE using thelocation measurements.

There may be some implementations (18) of the above described locationserver (17), wherein the at least one processor is configured to beginvia the external interface the first user plane location session withthe UE by being configured to send via the external interface a firstmessage to the UE or receive via the external interface a second messagefrom the UE, wherein the at least one processor is configured to beginvia the external interface the second user plane location session withthe UE by being configured to send via the external interface a thirdmessage to the UE or receive via the external interface a fourth messagefrom the UE, wherein the first message and the third message comprise afirst message type and the second message and the fourth messagecomprise a second message type.

There may be some implementations (19) of the above described locationserver (18), wherein the first message type is a Secure User PlaneLocation (SUPL) INIT message type and the second message type is a SUPLSTART message type.

There may be some implementations (20) of the above described locationserver (17), wherein the at least one processor is configured to end viathe external interface the first user plane location session with the UEby being configure to send via the external interface a fifth message tothe UE or receive via the external interface a sixth message from theUE.

There may be some implementations (21) of the above described locationserver (20), wherein the fifth message and the sixth message are each aSecure User Plane Location (SUPL) END message.

There may be some implementations (22) of the above described locationserver (20), wherein the indication that the UE will enter the idlestate comprises a parameter, flag, cause value, error cause value,LocationError value or Status Code value in a seventh message receivedfrom the UE.

There may be some implementations (23) of the above described locationserver (22), wherein the indication that the UE will enter the idlestate further comprises an estimate of a time interval between a time ofentering the idle state at the UE and a time of re-entering a connectedstate at the UE.

There may be some implementations (24) of the above described locationserver (22), wherein the seventh message comprises the sixth message ora positioning protocol message.

There may be some implementations (25) of the above described locationserver (24), wherein the positioning protocol message comprises a LongTerm Evolution (LTE) Positioning Protocol (LPP) Provide LocationInformation (PLI) message, wherein the LPP PLI message is received bythe location server in a Secure User Plane Location (SUPL) POS message.

There may be some implementations (26) of the above described locationserver (18), the at least one processor is further configured to:receive via the external interface the second message, wherein thesecond message comprises a first application identification (ID);receive via the external interface the fourth message, wherein thefourth message comprises a second application ID; verify the firstapplication ID is the same as the second application ID; and determinethe location of the UE using the location measurements, based on theverification.

There may be some implementations (27) of the above described locationserver (18), the at least one processor is further configured to: sendvia the external interface the first message, wherein the first messagecomprises a notification; and send via the external interface the thirdmessage, wherein the third message comprises the notification.

There may be some implementations (28) of the above described locationserver (18), the at least one processor is further configured to:receive via the external interface the fourth message, wherein thefourth message comprises a new session identification (ID); verify thenew session ID is associated with an initial session ID for the firstuser plane location session; and determine the location of the UE usingthe location measurements, based on the verification.

There may be some implementations (29) of the above described locationserver (18), the at least one processor is further configured to: sendvia the external interface the third message, wherein the third messagecomprises a new session identification (ID), wherein the new session IDis associated with an initial session ID for the first user planelocation session.

There may be some implementations (30) of the above described locationserver (17), the at least one processor is further configured to sendvia the external interface the location of the UE to an external client.

There may be some implementations (31) of the above described locationserver (17), the at least one processor is further configured to sendvia the external interface the location of the UE to the UE.

There may be some implementations (32) of the above described locationserver (17), wherein the user equipment (UE) is connected to thewireless network using Narrowband Internet of Things (NB-IoT) radioaccess or a narrowband New Radio (NR) radio access.

One implementation (33) may be a location server for supporting locationservices for a user equipment (UE), comprising: means for beginning afirst user plane location session with the UE; means for sending arequest for location measurements to the UE; means for receiving anindication from the UE that the UE will enter an idle state in which theUE will not be connected with a wireless network and during which the UEwill obtain the location measurements; means for ending the first userplane location session with the UE; means for beginning a second userplane location session with the UE; means for receiving the locationmeasurements from the UE using the second user plane location session;and means for determining the location of the UE using the locationmeasurements.

One implementation (33) may be a non-transitory storage medium includingprogram code stored thereon, the program code is operable to cause atleast one processor in a location server capable of supporting locationservices for a user equipment (UE) to: begin a first user plane locationsession with the UE; send a request for location measurements to the UE;receive an indication from the UE that the UE will enter an idle statein which the UE will not be connected with a wireless network and duringwhich the UE will obtain the location measurements; end the first userplane location session with the UE; begin a second user plane locationsession with the UE; receive the location measurements from the UE usingthe second user plane location session; and determine the location ofthe UE using the location measurements.

Therefore, it is intended that claimed subject matter not be limited tothe particular examples disclosed, but that such claimed subject mattermay also include all aspects falling within the scope of appendedclaims, and equivalents thereof.

What is claimed is:
 1. A method for supporting location services for auser equipment (UE) performed by the UE, comprising: beginning a firstuser plane location session with a location server; receiving a requestfor location measurements from the location server; sending anindication to the location server that the UE will enter an idle statein which the UE will not be connected with a wireless network; endingthe first user plane location session with the location server; enteringthe idle state; obtaining the location measurements while in the idlestate; re-entering a connected state with the wireless network;beginning a second user plane location session with the location server;and sending the location measurements to the location server using thesecond user plane location session.
 2. The method of claim 1, whereinbeginning the first user plane location session with the location servercomprises sending a first message to the location server or receiving asecond message from the location server, wherein beginning the seconduser plane location session with the location server comprises sending athird message to the location server or receiving a fourth message fromthe location server, wherein the first message and the third messagecomprise a first message type and the second message and the fourthmessage comprise a second message type.
 3. The method of claim 2,wherein the first message type is a Secure User Plane Location (SUPL)START message type and the second message type is a SUPL INIT messagetype.
 4. The method of claim 1, wherein ending the first user planelocation session with the location server comprises sending a fifthmessage to the location server or receiving a sixth message from thelocation server.
 5. The method of claim 4, wherein the fifth message andthe sixth message are each a Secure User Plane Location (SUPL) ENDmessage.
 6. The method of claim 4, wherein the indication that the UEwill enter the idle state comprises a parameter, flag, cause value,error cause value, LocationError value or Status Code value in a seventhmessage sent to the location server.
 7. The method of claim 6, whereinthe indication that the UE will enter the idle state further comprisesan estimate of a time interval between a time of entering the idle stateand a time of re-entering the connected state.
 8. The method of claim 6,wherein the seventh message comprises the fifth message or a positioningprotocol message.
 9. The method of claim 8, wherein the positioningprotocol message comprises a Long Term Evolution (LTE) PositioningProtocol (LPP) Provide Location Information (PLI) message, wherein theLPP PLI message is sent to the location server in a Secure User PlaneLocation (SUPL) POS message.
 10. The method of claim 2, furthercomprising: receiving the second message, wherein the second messagecomprises a first notification parameter; receiving the fourth message,wherein the fourth message comprises a second notification parameter;verifying the first notification parameter is the same as the secondnotification parameter; and sending the location measurements to thelocation server using the second user plane location session, based onthe verification.
 11. The method of claim 2, further comprising: sendingthe first message, wherein the first message comprises an applicationidentification (ID); and sending the third message, wherein the thirdmessage comprises the application ID.
 12. The method of claim 2, furthercomprising: receiving the fourth message, wherein the fourth messagecomprises a new session identification (ID); verifying the new sessionID is associated with an initial session ID for the first user planelocation session; and sending the location measurements to the locationserver using the second user plane location session, based on theverification.
 13. The method of claim 2, further comprising: sending thethird message, wherein the third message comprises a new sessionidentification (ID), wherein the new session ID is associated with aninitial session ID for the first user plane location session.
 14. Themethod of claim 1, wherein the user equipment (UE) is connected to thewireless network using Narrowband Internet of Things (NB-IoT) radioaccess or a narrowband New Radio (NR) radio access.
 15. A user equipment(UE) capable of supporting location services, comprising: at least onewireless transceiver configured to wirelessly communicate with awireless network; and at least one processor coupled to the at least onewireless transceiver and configured to: begin via the at least onewireless transceiver a first user plane location session with a locationserver; receive via the at least one wireless transceiver a request forlocation measurements from the location server; send via the at leastone wireless transceiver an indication to the location server that theUE will enter an idle state in which the UE will not be connected withthe wireless network; end via the at least one wireless transceiver thefirst user plane location session with the location server; enter theidle state; obtain via the at least one wireless transceiver thelocation measurements while in the idle state; re-enter a connectedstate with the wireless network; begin via the at least one wirelesstransceiver a second user plane location session with the locationserver; and send via the at least one wireless transceiver the locationmeasurements to the location server using the second user plane locationsession.
 16. The UE of claim 15, wherein the at least one processor isconfigured to begin via the at least one wireless transceiver the firstuser plane location session with the location server by being configuredto send via the at least one wireless transceiver a first message to thelocation server or receive via the at least one wireless transceiver asecond message from the location server, wherein the at least oneprocessor is configured to begin via the at least one wirelesstransceiver the second user plane location session with the locationserver by being configured to send via the at least one wirelesstransceiver a third message to the location server or receive via the atleast one wireless transceiver a fourth message from the locationserver, wherein the first message and the third message comprise a firstmessage type and the second message and the fourth message comprise asecond message type.
 17. The UE of claim 16, wherein the first messagetype is a Secure User Plane Location (SUPL) START message type and thesecond message type is a SUPL INIT message type.
 18. The UE of claim 15,wherein the at least one processor is configured to end via the at leastone wireless transceiver the first user plane location session with thelocation server by being configured to send via the at least onewireless transceiver a fifth message to the location server or receivevia the at least one wireless transceiver a sixth message from thelocation server.
 19. The UE of claim 18, wherein the fifth message andthe sixth message are each a Secure User Plane Location (SUPL) ENDmessage.
 20. The UE of claim 18, wherein the indication that the UE willenter the idle state comprises a parameter, flag, cause value, errorcause value, LocationError value or Status Code value in a seventhmessage sent to the location server.
 21. The UE of claim 20, wherein theindication that the UE will enter the idle state further comprises anestimate of a time interval between a time of entering the idle stateand a time of re-entering the connected state.
 22. The UE of claim 20,wherein the seventh message comprises the fifth message or a positioningprotocol message.
 23. The UE of claim 22, wherein the positioningprotocol message comprises a Long Term Evolution (LTE) PositioningProtocol (LPP) Provide Location Information (PLI) message, wherein theLPP PLI message is sent to the location server in a Secure User PlaneLocation (SUPL) POS message.
 24. The UE of claim 16, the at least oneprocessor is further configured to: receive via the at least onewireless transceiver the second message, wherein the second messagecomprises a first notification parameter; receive via the at least onewireless transceiver the fourth message, wherein the fourth messagecomprises a second notification parameter; verify the first notificationparameter is the same as the second notification parameter; and send viathe at least one wireless transceiver the location measurements to thelocation server using the second user plane location session, based onthe verification.
 25. The UE of claim 16, the at least one processor isfurther configured to: send via the at least one wireless transceiverthe first message, wherein the first message comprises an applicationidentification (ID); and send via the at least one wireless transceiverthe third message, wherein the third message comprises the applicationID.
 26. The UE of claim 16, the at least one processor is furtherconfigured to: receive via the at least one wireless transceiver thefourth message, wherein the fourth message comprises a new sessionidentification (ID); verify the new session ID is associated with aninitial session ID for the first user plane location session; and sendvia the at least one wireless transceiver the location measurements tothe location server using the second user plane location session, basedon the verification.
 27. The UE of claim 16, the at least one processoris further configured to: send via the at least one wireless transceiverthe third message, wherein the third message comprises a new sessionidentification (ID), wherein the new session ID is associated with aninitial session ID for the first user plane location session.
 28. The UEof claim 15, wherein the UE is connected to the wireless network usingNarrowband Internet of Things (NB-IoT) radio access or a narrowband NewRadio (NR) radio access.
 29. A user equipment (UE) capable of supportinglocation services, comprising: means for beginning a first user planelocation session with a location server; means for receiving a requestfor location measurements from the location server; means for sending anindication to the location server that the UE will enter an idle statein which the UE will not be connected with a wireless network; means forending the first user plane location session with the location server;means for entering the idle state; means for obtaining the locationmeasurements while in the idle state; means for re-entering a connectedstate with the wireless network; means for beginning a second user planelocation session with the location server; and means for sending thelocation measurements to the location server using the second user planelocation session.
 30. A non-transitory storage medium including programcode stored thereon, the program code is operable to cause at least oneprocessor in a user equipment (UE) capable of supporting locationservices to: begin a first user plane location session with a locationserver; receive a request for location measurements from the locationserver; send an indication to the location server that the UE will enteran idle state in which the UE will not be connected with a wirelessnetwork; end the first user plane location session with the locationserver; enter the idle state; obtain the location measurements while inthe idle state; re-enter a connected state with the wireless network;begin a second user plane location session with the location server; andsend the location measurements to the location server using the seconduser plane location session.